Prioritized issue groups from the latest Plugin Check scan
Maintainability
274
9 issue groups
Security
46
6 issue groups
Repo Compliance
3
3 issue groups
I18n
1
1 issue group
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$checked".
Sample message
Processing form data without nonce verification.
Sample message
print_r() found. Debug code should not normally be used in production.
Sample message
$_GET[$key] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Processing form data without nonce verification.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "active_plugins".
Sample message
var_dump() found. Debug code should not normally be used in production.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'addslashes'.
Sample message
Detected usage of a non-sanitized input variable: $_GET[$key]
Sample message
Detected usage of a possibly undefined superglobal array index: $_SERVER['REQUEST_METHOD']. Check that the array index exists before using it.
Sample message
Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.
Sample message
Editor blocks must define "apiVersion" 3 or higher in block.json for WordPress 7.0+ iframe editor compatibility.
Sample message
File has mixed line endings; this may cause incorrect results
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
Plugin name "Apaczka: integracja z WooCommerce" is different from the name declared in plugin header "Apaczka.pl".
Sample message
Tested up to: 6.9 < 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 readme description contains unofficial language. It must be written in standard English.
Sample message
The readme short description contains unofficial language. It must be written in standard English.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Apaczka: integracja z WooCommerce" - contains the restricted term "woocommerce" which cannot be used within in your plugin name, unless your plugin name contains one of the allowed patterns: "for woocommerce", "with woocommerce", "using woocommerce", or "and woocommerce". The term must still not appear anywhere else in your name.
Not analyzed yet.
First score snapshot
v1.4.3
37
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 37 | 324 | 8 | 316 | v1.4.3 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.