Prioritized issue groups from the latest Plugin Check scan
Security
56
7 issue groups
Maintainability
31
12 issue groups
Repo Compliance
1
1 issue group
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$args['after_title']'.
Sample message
Processing form data without nonce verification.
Sample message
Function "register_block_type()" requires WordPress 5.0.0, but your plugin minimum supported version is WordPress 4.0.0.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "SMLY4WP_PLUGIN_FILE".
Sample message
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Smaily for WP" - contains the restricted term "wp" which cannot be used at all in your plugin name.
Sample message
Attempting a database schema change is discouraged.
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a non-sanitized input variable: $_POST['form_data']
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST['form_data']. Check that the array index exists before using it.
Sample message
$_POST['form_data'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "run_smaily_for_wp".
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$upgrade".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$file_name'.
Sample message
Version parameter is not explicitly set or has been set to an equivalent of "false" for wp_enqueue_script; This means that the WordPress core version will be used which is not recommended for plugin or theme development.
Sample message
Editor blocks must define "apiVersion" 3 or higher in block.json for WordPress 7.0+ iframe editor compatibility.
Sample message
The "/vendor" directory using composer exists, but "composer.json" file is missing.
Sample message
Tested up to: 6.4 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.
Potential connections found in static code analysis.
Outbound calls
23
External assets
0
Incoming endpoints
2
No external asset domains detected.
No public endpoints detected.
wp_ajax
wp_ajax
First score snapshot
v3.1.7
39
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 39 | 88 | 52 | 36 | v3.1.7 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.