Floating button for chatting with your visitors via WhatsApp, Messenger, Contact form, and more.
Category Scores
Top Issues by Category
maintainability18
security12
Issues Details
34 issues found in latest scan
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "add_whatshelp_code".
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"\n\n<!-- GetButton.io widget -->\n<script data-no-optimize=\"1\" defer src=\"https://static.getbutton.io/widget/bundle.js?id=${id}\"></script>\n<!-- /GetButton.io widget -->\n\n"'.
Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found interpolation in unescaped heredoc.
Function "esc_attr()" requires WordPress 2.8.0, but your plugin minimum supported version is WordPress 2.7.0.
Mismatched text domain. Expected 'whatshelp-chat-button' but got 'getbutton'.
Sanitization missing for register_setting().
Using __FILE__ for menu slugs risks exposing filesystem structure.
Scripts must be registered/enqueued via wp_enqueue_script()
Plugin name "Chat Button & Custom ChatGPT-Powered Bot by GetButton.io" is different from the name declared in plugin header "Chat Button by GetButton.io (ex. WhatsHelp)".
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Tested up to: 6.8 < 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.
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
| Code | Type | Message | Count |
|---|---|---|---|
| WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedFunctionFound | WARNING | Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "add_whatshelp_code". | 6 |
| WordPress.Security.EscapeOutput.OutputNotEscaped | ERROR | All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"\n\n<!-- GetButton.io widget -->\n<script data-no-optimize=\"1\" defer src=\"https://static.getbutton.io/widget/bundle.js?id=${id}\"></script>\n<!-- /GetButton.io widget -->\n\n"'. | 6 |
| PluginCheck.CodeAnalysis.Heredoc.NotAllowed | ERROR | Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead | 5 |
| WordPress.Security.EscapeOutput.HeredocOutputNotEscaped | ERROR | All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found interpolation in unescaped heredoc. | 4 |
| wp_function_not_compatible_with_requires_wp | ERROR | Function "esc_attr()" requires WordPress 2.8.0, but your plugin minimum supported version is WordPress 2.7.0. | 4 |
| WordPress.WP.I18n.TextDomainMismatch | ERROR | Mismatched text domain. Expected 'whatshelp-chat-button' but got 'getbutton'. | 2 |
| PluginCheck.CodeAnalysis.SettingSanitization.register_settingMissing | ERROR | Sanitization missing for register_setting(). | 1 |
| WordPress.Security.PluginMenuSlug.Using__FILE__ | WARNING | Using __FILE__ for menu slugs risks exposing filesystem structure. | 1 |
| WordPress.WP.EnqueuedResources.NonEnqueuedScript | ERROR | Scripts must be registered/enqueued via wp_enqueue_script() | 1 |
| mismatched_plugin_name | WARNING | Plugin name "Chat Button & Custom ChatGPT-Powered Bot by GetButton.io" is different from the name declared in plugin header "Chat Button by GetButton.io (ex. WhatsHelp)". | 1 |
| missing_direct_file_access_protection | ERROR | PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit; | 1 |
| outdated_tested_upto_header | ERROR | Tested up to: 6.8 < 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. | 1 |
| plugin_header_no_license | ERROR | Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license. | 1 |
Latest Snapshot
Findings
34
Errors
26
Warnings
8
Score History
First score snapshot
First scan completed Jun 20, 2026
v1.9.2 · Plugin Check 2.0.0 · Model 2026.06-mvp-static-v2
Jun 20, 2026
v1.9.2
58
Latest
- Findings
- 34
- Errors
- 26
- Warnings
- 8
- Plugin Check
- 2.0.0
- Model
- 2026.06-mvp-static-v2
| Scan | Score | Findings | Errors | Warnings | Plugin | Plugin Check | Model |
|---|---|---|---|---|---|---|---|
| Jun 20, 2026Latest | 58 | 34 | 26 | 8 | v1.9.2 | 2.0.0 | 2026.06-mvp-static-v2 |