Plugin Check (PCP)
Plugin Check is a WordPress.org tool which provides checks to help plugins meet the directory requirements and follow various best practices.
Choix
Yes — Plugin Check (PCP) is a safe, well-maintained plugin to use in 2026. It runs on 10K+ sites, is rated 4.5/5 and was last updated 2 weeks ago, and scores 87/100 on our health check.
- Prouvé à grande échelle sur plus de 10 000 sites actifs
- Aimé par les utilisateurs — 4,5/5 sur 36 avis
- Développé activement — Dernière mise à jour il y a 2 semaines
- Momentum — downloads up 32.6% vs the previous 30 days
Comment s'accumule-t-il ?
Côte à côte sur les installations, les mises à jour, les évaluations et le supportTéléchargements quotidiens
Les pics de téléchargement suivent généralement une nouvelle version - chaque site qui met à jour automatiquement compte comme un téléchargement.
Classements
Where Plugin Check (PCP) stands todayWordPress.org Classements de recherche
Position en direct dans la recherche de plugins, Top 100| Mot-clé | Position |
|---|---|
| accessibilité | >100 |
| performance | >100 |
| plugin best practices | #2 |
| la sécurité | >100 |
| essai | #40 |
Adoption de version
Part de sites actifs par version.
Répartition des notes
★★★★★ ★★★★★ 4,5 sur 36 avis
About Plugin Check (PCP)
À partir du Lisezmoi officiel · v2.2.0Description
Plugin Check is a tool for testing whether your plugin meets the required standards for the WordPress.org plugin directory. With this plugin you will be able to run most of the checks used for new submissions, and check if your plugin meets the requirements.
Additionally, the tool flags violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices.
The checks can be run either using the WP Admin user interface or WP-CLI:
- To check a plugin using WP Admin, please navigate to the Tools > Plugin Check menu. You need to be able to manage plugins on your site in order to access that screen.
- To check a plugin using WP-CLI, please use the
wp plugin checkcommand. For example, to check the “Hello Dolly” plugin:wp plugin check hello.php- Note that by default when using WP-CLI, only static checks can be executed. In order to also include runtime checks, a workaround is currently necessary using the
--requireargument of WP-CLI, to manually load thecli.phpfile within the plugin checker directory before WordPress is loaded. For example:wp plugin check hello.php --require=./wp-content/plugins/plugin-check/cli.php - You could use arbitrary path or URL to check a plugin. For example, to check a plugin from a URL:
wp plugin check https://example.com/plugin.zipor to check a plugin from a path:wp plugin check /path/to/plugin
- Note that by default when using WP-CLI, only static checks can be executed. In order to also include runtime checks, a workaround is currently necessary using the
The checks are grouped into several categories, so that you can customize which kinds of checks you would like to run on a plugin.
Keep in mind that this plugin is not a replacement for the manual review process, but it will help you speed up the process of getting your plugin approved for the WordPress.org plugin repository, and it will also help you avoid some common mistakes.
Even if you do not intend to host your plugin in the WordPress.org directory, you are encouraged to use Plugin Check so that your plugin follows the base requirements and best practices for WordPress plugins.
Plugin Namer Tool
Plugin Check now includes an AI-powered Plugin Namer tool (accessible via Tools > Plugin Check Namer) that helps plugin authors evaluate plugin names before submission. This tool checks for:
- Similarity to existing plugins in the WordPress.org directory
- Potential trademark conflicts with well-known brands
- Compliance with WordPress plugin naming guidelines
- Generic or overly broad naming issues
The Plugin Namer provides instant feedback with actionable suggestions, helping you choose a clear, unique, and policy-compliant name that stands out in the plugin directory. This feature requires WordPress 7.0+ and configured AI connectors.
Important: The Plugin Namer tool provides guidance only and is not definitive. All plugin name decisions are subject to final review and approval by the WordPress.org Plugins team reviewers.
SVN Checker Tool
Plugin Check also includes an SVN Checker tool (accessible via Tools > Plugin Check SVN) that scans a plugin’s WordPress.org SVN repository for unexpected files, folders, and zip archives. This helps plugin authors and reviewers ensure that only the intended files are present in the plugin’s trunk, tags, and assets directories before or after a release.
Checks reviewed by AI
When AI analysis is enabled, Plugin Check can review selected results to help identify likely false positives. Related issues are grouped and analyzed with prompts tailored to the type of check, using the surrounding code as context. The AI review does not remove or change the original results, but adds an additional summary that highlights which findings may need human review before taking action.
Installation
Installation à partir de WordPress
- Visitez plugins > Ajouter nouveau.
- Search for Plugin Check.
- Install and activate the Plugin Check plugin.
Installation manuelle
- Upload the entire
plugin-checkfolder to the/wp-content/plugins/directory. - Visitez plugins.
- Activate the Plugin Check plugin.
Journal de modifications
2.2.0
- Enhancement – Add React usage check to detect React 19 incompatibilities.
- Enhancement – Add
menu_image_iconcheck to detect raster image admin menu icons. - Enhancement – Add sniff to detect direct access to AI Connector API keys.
- Enhancement – Add opt-in
.pcpignoreexclusions. - Enhancement – Enforce “Tested up to” exclusively in the readme file.
- Enhancement – Allow includes of safe files in the direct file access check.
- Enhancement – Reject unknown categories in
wp plugin checkandwp plugin list-checks. - Enhancement – Add Blue Oak license to the allowed licenses.
- Enhancement – Clarify the
Requires Pluginsdirectory availability warning. - Enhancement – Make the AI false-positive summary translatable.
- Enhancement – Improve AI sanitization prompt to avoid false positives for password, token, and API key fields.
- Enhancement – Improve admin UI accessibility.
- Fix – Fix false positive for the
auto_update_pluginsoption. - Fix – Fix “Check it!” button failing silently with a nonce error.
- Fix – Define plugin constants when
cli.phpis loaded without the plugin active. - Chore – Document check result codes and severity.
- Chore – Add unit test coverage for
Amend_Check_Result,Readme_UtilsandIgnore_Matcher. - Chore – Update WordPress function since dataset.
- Chore – Update Playground PR preview workflow.
- Chore – Update development and CI dependencies.
2.1.0
- Enhancement – Add SVN Checker to detect unexpected files, folders, and zip archives in plugin SVN repositories.
- Enhancement – Add PHP Error Reporting check to detect production-time changes to PHP error reporting settings.
- Enhancement – Add AI Provider check to recommend the WordPress AI Client.
- Enhancement – Validate each
Requires Pluginsdependency individually against the WordPress.org plugin directory. - Enhancement – Use distinct visual styles for different issue types in results.
- Fix – Preserve Unicode characters in exported results.
- Fix – Fix silently dropped WordPress core functions in the since-data generator.
- Fix – Decouple AJAX calls in the admin UI and remove unnecessary return values.
- Chore – Add AI features and configuration documentation.
- Chore – Update WordPress function since dataset.
- Chore – Update development and CI dependencies.
2.0.0
- Enhancement – Add WordPress functions compatibility check to flag usage of functions unavailable in a plugin’s declared minimum WordPress version.
- Enhancement – Add Write File check to detect plugins saving data in the plugin folder instead of the uploads directory or database.
- Enhancement – Add batched AI false positive detection with check-specific prompts and AI model selection for WP-CLI.
- Enhancement – Add CTRF export support for check results.
- Enhancement – Add an error count summary to the Plugin Check UI.
- Enhancement – Improve Direct File Access detection for library-style files.
- Enhancement – Adjust checks for update mode.
- Fix – Relax Update URI header validation for WordPress.org plugin URLs.
- Fix – Improve WordPress functions compatibility detection to avoid PHP serialization false positives.
- Fix – Respect
wp_supports_ai()and text-capable model filtering in the Plugin Namer. - Fix – Show Plugin Namer token usage in results.
- Fix – Recognize EUPL as a GPL-compatible license.
- Fix – Improve internationalization for emoji-prefixed labels.
- Fix – Update PHPCS sniffer repository links.
- Tweak – Update WP-CLI runtime checks documentation.
- Chore – Add automated WordPress function compatibility data generation.
- Chore – Add AI usage disclosure to the pull request template.
- Chore – Add AI coding agent instructions.
- Chore – Clean up wp-env development and test configuration warnings.
- Chore – Show a WordPress Playground preview button on pull requests.
- Chore – Update development and CI dependencies.
1.9.0
- Enhancement – Use the WordPress 7.0 core AI connectors.
- Enhancement – Add External Admin Menu Links check to detect external URLs in top-level admin menus.
- Enhancement – Add and refine the block metadata compatibility check to require
apiVersion3+ for WordPress 7.0+ iframe editor compatibility, including adjusted severity by mode. - Enhancement – Improve Plugin Updater detection to identify Plugin Update Checker (PUC) calls.
- Enhancement – Accept WTFPL as a GPL-compatible license.
- Fix – Improve PayPal donation URL validation for complex query strings.
- Fix – Ensure AI Check uses the configured model preference.
- Fix – Show a clear Plugin Namer error message when AI connector status is unavailable.
- Fix – Update the Plugin Namer connector settings page link.
- Tweak – Convert the
load_plugin_textdomain()check from error to warning severity. - Fix – Improve readme contributors validation when trailing commas are present.
- Fix – Make markdown file checks case-insensitive.
- Tweak – Refine escaping sniff error messages for clearer guidance.
- Chore – Update development dependencies, including
@wordpress/scripts,simple-git,basic-ftp,svgo,immutable, and@wp-playground/cli. - Tweak – Update WordPress.org Plugins Team naming for consistency.
1.8.0
- Enhancement – Add AI-powered Plugin Namer tool to evaluate plugin names for trademark conflicts and naming best practices.
- Enhancement – Add AI Instructions Detection Check to identify AI tool configuration files and development-only directories.
- Enhancement – Add support for exporting check results in CSV, JSON, and Markdown formats.
- Enhancement – Add check type filter to allow filtering results by errors and warnings.
- Enhancement – Add Direct File Access check to ensure proper security validation with ABSPATH constant.
- Enhancement – Add check for mismatched “Tested up to” header between plugin header and readme.txt.
- Enhancement – Update trademark check to remove acronym exceptions and improve flexibility.
- Enhancement – Add heredoc sniff to detect and restrict heredoc usage (nowdoc allowed).
- Fix – Update Playground integration blueprint for compatibility.
- Fix – Force correct plugin slug detection in WP-CLI command.
1.7.0
- Enhancement – Add Minified File Detection Check to identify and handle minified files in plugins.
- Enhancement – Implement check for insecure use of wp_verify_nonce() to improve security validation.
- Enhancement – Add direct database query sniff to detect direct database calls without using WordPress functions.
- Enhancement – Add prefixing check to ensure proper function and class name prefixing.
- Enhancement – Update localhost sniff regex to improve detection of localhost URLs including *.local domains.
- Enhancement – Disallow runtime checks when custom user table constants are defined for better compatibility.
- Enhancement – Add forbidden functions check to detect usage of disallowed PHP functions.
- Enhancement – New check for wp_safe_redirect to encourage use of WordPress safe redirect function.
- Enhancement – Improve mismatched text domain check for better internationalization validation.
- Enhancement – Detect links that request five-star reviews to enforce plugin directory guidelines.
- Enhancement – Add The Unlicense to GPL-compatible license check.
- Enhancement – Improve localhost sniff code for more accurate detection.
- Fix – Ignore vendor_prefixed and vendor-prefixed folders in checks to prevent false positives.
- Fix – Handle possible empty element in scanner to prevent PHP warnings.
- Fix – Hide error output in scanner for cleaner output.
- Fix – Call ReflectionProperty::setAccessible() only in older PHP versions for better PHP 8.1+ compatibility.
- Fix – Prevent deletion of custom WordPress tables during cleanup in test environment.
Pour les développeurs
Est-ce votre plugin ? Montrez les chiffres.
Ajoutez un badge en direct à votre site, docs ou github readme. Il se met à jour par lui-même - aucun compte n'est nécessaire.
Best Plugin Check (PCP) alternatives
Tous les plugins d'accessibilité →FAQ
Plugin Check (PCP): quick answers
Réponses directes, extraites des données en direct WordPress.org.
Source : WordPress.org
Is Plugin Check (PCP) free?
Yes. Plugin Check (PCP) is free to download and use from the official WordPress.org plugin directory.
Is Plugin Check (PCP) safe to use in 2026?
Yes — Plugin Check (PCP) is a safe, well-maintained plugin to use in 2026. It runs on 10K+ sites, is rated 4.5/5 and was last updated 2 weeks ago, and scores 87/100 on our health check.
How many websites use Plugin Check (PCP)?
Plugin Check (PCP) is active on 10K+ WordPress websites and has been downloaded 1,832,966 times since it launched in September 2011. It was downloaded 270,013 times in the last 30 days.
Does Plugin Check (PCP) work with WordPress 7.1?
Plugin Check (PCP) is officially tested up to WordPress 7.0.9, while the latest release is 7.1.5. It may still work, but try it on a staging site first.
What PHP version does Plugin Check (PCP) need?
Plugin Check (PCP) requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Plugin Check (PCP) last updated?
The latest version, 2.2.0, was released on November 6, 2026 (2 weeks ago).
Who makes Plugin Check (PCP)?
Plugin Check (PCP) is developed and maintained by WordPress.org.
What are the best alternatives to Plugin Check (PCP)?
The most popular alternatives to Plugin Check (PCP) are Web Accessibility (formally… (500K+ installs), Auto Image Attributes From… (100K+ installs) and Accessibility by UserWay (80K+ installs).
Propulsé par PageForge
Un modèle et une feuille de calcul. Une vraie page pour chaque recherche.
PageForge transforme chaque ligne d'un CSV en une page WordPress avec son propre titre, URL, SEO et schéma, construit sur la mise en page que vous Déjà conçu. Gratuit sur WordPress.org.
- CSV et XLSX, plus Google Sheets sur les professionnels et les entreprises
- Son propre titre, URL, SEO champs et schéma pour chaque page
- Fonctionne avec l'éditeur de blocs, Elementor, Divi et Avada
- Gratuit sur WordPress.org, pas de carte de crédit
