If someone wants to leave your WordPress, let them go.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
35
10 issue groups
Security
34
9 issue groups
I18n
10
3 issue groups
Supply Chain
1
1 issue group
Sample message
Namespaces declared by a theme/plugin should start with the theme/plugin prefix. Found: "NeverLetMeGo".
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$count".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$level'.
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
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead
Sample message
Use of a direct database call is discouraged.
Sample message
Use placeholders and $wpdb->prepare(); found $query
Sample message
Processing form data without nonce verification.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.
Sample message
Detected usage of a non-sanitized input variable: $_GET[$name]
Sample message
$_GET[$name] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "never_let_me_go".
Sample message
Processing form data without nonce verification.
Sample message
load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.
Sample message
Unescaped parameter $sql used in $wpdb->query()\n$sql assigned unsafely at line 236.
Sample message
Detected usage of meta_query, possible slow query.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "NeverLetMeGo".
Sample message
Translatable string should not be wrapped in HTML. Found: '<strong>[Never Let Me Go] Plugin is active but features are not enabled. Please go to <a href="%s">setting page</a>.</strong>'
Sample message
Hidden files are not permitted.
Sample message
The "/vendor" directory using composer exists, but "composer.json" file is missing.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Tested up to: 6.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.
Potential connections found in static code analysis.
Outbound calls
9
External assets
0
Incoming endpoints
2
No external asset domains detected.
register_rest_route
wp_ajax
First score snapshot
v2.0.3
35
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 35 | 81 | 34 | 47 | v2.0.3 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.