Google reCAPTCHA v2 for bbPress is a free plugin/add-on for bbPress, that allow you to easily add Google reCAPTCHA v2 on your bbPress forum.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
21
13 issue groups
Security
7
4 issue groups
Repo Compliance
3
3 issue groups
I18n
2
2 issue groups
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "rfb_add_recaptcha_key_field".
Sample message
Detected usage of a non-sanitized input variable: $_POST['g-recaptcha-response']
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST['g-recaptcha-response']. Check that the array index exists before using it.
Sample message
$_POST['g-recaptcha-response'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
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
Processing form data without nonce verification.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fsockopen().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
The parameter "FALSE" at position #2 of load_plugin_textdomain() has been deprecated since WordPress version 2.7.0. Use "" instead.
Sample message
Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.
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
Tested up to: 6.7 < 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
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Sample message
The "Domain Path" header in the plugin file must point to an existing folder. Found: "languages"
Sample message
Mismatched Stable Tag: 1.0.5 != 1.0.8. 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
23
External assets
1
Incoming endpoints
0
No public endpoints detected.
First score snapshot
v1.0.8
75
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 75 | 33 | 14 | 19 | v1.0.8 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.