Prioritized issue groups from the latest Plugin Check scan
Security
77
6 issue groups
I18n
31
2 issue groups
Maintainability
13
7 issue groups
Repo Compliance
3
3 issue groups
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
Multiple placeholders in translatable strings should be ordered. Expected "%1$s, %2$s", but got "%s, %s" in 'Language %s one of %s'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$this'.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "active_plugins".
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a non-sanitized input variable: $_REQUEST['alert-type']
Sample message
$_REQUEST['alert-type'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
Sample message
Detected usage of a possibly undefined superglobal array index: $_SERVER['HTTP_HOST']. Check that the array index exists before using it.
Sample message
The use of function eval() is forbidden
Sample message
Found call to wp_enqueue_script() with external resource. Offloading scripts to your servers or any remote service is disallowed.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "ifVisibilityRulesPrepare".
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Tested up to: 5.6 < 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.
Sample message
The "Requires at least" field was ignored. This field should only contain a valid WordPress version such as "7.0" or "6.9".
Sample message
One or more tags were ignored. Please limit your plugin to 5 tags.
Sample message
Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.
Potential connections found in static code analysis.
Outbound calls
17
External assets
2
Incoming endpoints
0
No public endpoints detected.
First score snapshot
v0.5
40
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 40 | 124 | 99 | 25 | v0.5 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.