Pure Metafields is very light weight plugin tused to create custom metabox for any post type like page, post and your custom post type support it.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
596
11 issue groups
Security
80
7 issue groups
I18n
26
3 issue groups
Repo Compliance
1
1 issue group
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$_carrier_json".
Sample message
Mismatched text domain. Expected 'pure-metafields' but got 'finzo'.
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a non-sanitized input variable: $_POST[$field['id']]
Sample message
$_POST[$field['id']] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$_grd_name'.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "tp_meta_boxes".
Sample message
Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead
Sample message
Detected usage of meta_query, possible slow query.
Sample message
Detected usage of tax_query, possible slow query.
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST[$repeater_field['id']]. Check that the array index exists before using it.
Sample message
Processing form data without nonce verification.
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 _n() 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
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
debug_backtrace() found. Debug code should not normally be used in production.
Sample message
error_log() found. Debug code should not normally be used in production.
Sample message
set_error_handler() found. Debug code should not normally be used in production.
Sample message
Plugin name "Pure Metafields" is different from the name declared in plugin header "PureFields – Meta Fields & Custom Post Type Builder".
Sample message
Tested up to: 6.9 < 7.1. 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
Mismatched Stable Tag: 1.7.0 != 1.7.3. 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.
Sample message
Unexpected markdown file "CLAUDE.md" detected in plugin root. Only specific markdown files are expected in production plugins.
Potential connections found in static code analysis.
Outbound calls
47
External assets
3
Incoming endpoints
6
No public endpoints detected.
wp_ajax
wp_ajax
wp_ajax
wp_ajax
wp_ajax
wp_ajax
2 score snapshots
v1.7.3
34
Latest
v1.4.9
53
Score
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 34 | 703 | 47 | 656 | v1.7.3 | 2.1.0 |
| 53 | 135 | 5 | 130 | v1.4.9 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.