Title: Plugin Check (PCP) Author: WordPress.org Published: 4 setembro, 2011 Last modified: 15 março, 2026 --- Pesquisar plugins ![](https://ps.w.org/plugin-check/assets/banner-772x250.png?rev=3166100) ![](https://ps.w.org/plugin-check/assets/icon.svg?rev=3166100) # Plugin Check (PCP) Por [WordPress.org](https://profiles.wordpress.org/wordpressdotorg/) [Baixar](https://downloads.wordpress.org/plugin/plugin-check.1.9.0.zip) [Pré-visualização ao vivo](https://br.wordpress.org/plugins/plugin-check/?preview=1) * [Detalhes](https://br.wordpress.org/plugins/plugin-check/#description) * [Avaliações](https://br.wordpress.org/plugins/plugin-check/#reviews) * [Instalação](https://br.wordpress.org/plugins/plugin-check/#installation) * [Desenvolvimento](https://br.wordpress.org/plugins/plugin-check/#developers) [Suporte](https://wordpress.org/support/plugin/plugin-check/) ## Descrição 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 check` command. 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 `--require` argument of WP-CLI, to manually load the `cli.php` file 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.zip` or to check a plugin from a path: `wp plugin check /path/to/plugin` 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. ## Instalação #### Installation from within WordPress 1. Visit **Plugins > Add New**. 2. Search for **Plugin Check**. 3. Install and activate the Plugin Check plugin. #### Manual installation 1. Upload the entire `plugin-check` folder to the `/wp-content/plugins/` directory. 2. Visit **Plugins**. 3. Activate the Plugin Check plugin. ## Perguntas frequentes ### Where can I contribute to the plugin? All development for this plugin is handled via [GitHub](https://github.com/WordPress/plugin-check/) any issues or pull requests should be posted there. ### What if the plugin reports something that’s correct as an “error” or “warning”? We strive to write a plugin in a way that minimizes false positives but if you find one, please report it in the GitHub repo. For certain false positives, such as those detected by PHPCodeSniffer, you may be able to annotate the code to ignore the specific problem for a specific line. ### Why does it flag something as bad? It’s not flagging “bad” things, as such. Plugin Check is designed to be a non-perfect way to test for compliance with the [Plugin Review guidelines](https://make.wordpress.org/plugins/handbook/performing-reviews/review-checklist/), as well as additional plugin development best practices in accessibility, performance, security and other areas. Not all plugins must adhere to these guidelines. The purpose of the checking tool is to ensure that plugins uploaded to the [central WordPress.org plugin repository](https://wordpress.org/plugins/) meet the latest standards of WordPress plugin and will work on a wide variety of sites. Many sites use custom plugins, and that’s perfectly okay. But plugins that are intended for use on many different kinds of sites by the public need to have a certain minimum level of capabilities, in order to ensure proper functioning in many different environments. The Plugin Review guidelines are created with that goal in mind. This plugin checker is not perfect, and never will be. It is only a tool to help plugin authors, or anybody else who wants to make their plugin more capable. All plugins submitted to WordPress.org are hand-reviewed by a team of experts. The automated plugin checker is meant to be a useful tool only, not an absolute system of measurement. ### Does a plugin need to pass all checks to be approved in the WordPress.org plugin directory? To be approved in the WordPress.org plugin directory, a plugin must typically pass all checks in the “Plugin repo” category. Other checks are additional and may not be required to pass. In any case, passing the checks in this tool likely helps to achieve a smooth plugin review process, but is no guarantee that a plugin will be approved in the WordPress. org plugin directory. ## Avaliações ![](https://secure.gravatar.com/avatar/5dd481438e5ca8e135c0520aaf922a34f2a908d8d0e8b358d8563debe0b04589? s=60&d=retro&r=g) ### 󠀁[False positives](https://wordpress.org/support/topic/false-positives-36/)󠁿 [Barry](https://profiles.wordpress.org/tmgm/) 19 março, 2026 1 resposta The plugin review started with false positives and was not accurate. ![](https://secure.gravatar.com/avatar/1db275a77ae016b63d1edc49625a6ba5d58b4f7552a272dcf3cf331e728812cc? s=60&d=retro&r=g) ### 󠀁[Must have](https://wordpress.org/support/topic/must-have-741/)󠁿 [Stachethemes](https://profiles.wordpress.org/stachethemes/) 3 fevereiro, 2026 Useful tool for catching issues early. If you’re serious about plugin development, this is a must-have. ![](https://secure.gravatar.com/avatar/a8fadf98d183bd5fb216b5ca07b5722d365e1a2412e5daa0f829c6fd11664783? s=60&d=retro&r=g) ### 󠀁[Very helpful](https://wordpress.org/support/topic/very-helpful-1572/)󠁿 [dansart](https://profiles.wordpress.org/dansart/) 29 janeiro, 2026 Great tool to help finding issues with your plugin. The only thing I would like to see as a button that allows you to ignore certain messages, or mark them as fixed. So if you re-scan, it is easier to see, what still needs to be done. Also helpful would be a better indicator how serious a issue is. I know there are Errors and Warnings, but maybe with a score? And “Error” in red and “Warning” in orange for better accessibility. ![](https://secure.gravatar.com/avatar/e02f782d76eb2b7113cc8477d3504e8b4aa34330634cdc34c0fff8e67c2db23b? s=60&d=retro&r=g) ### 󠀁[Amazingly useful](https://wordpress.org/support/topic/amazingly-useful-15/)󠁿 [muzKore](https://profiles.wordpress.org/muzoid/) 15 janeiro, 2026 This plugin helped me identify areas of my plugin that I thought I had taken care of. When developing my first plugin. I learned a lot through the feedback given and was able to re-run and eventually remove of all errors. On a side note, what I did discover was that a lot of the warnings were general and some were not really applicable to my plugin. It took time and research to work this out so don’t freak out if you get a heap of feedback from the plugin. Try to filter down to the errors, get them sorted and then move onto the warnings and fix what you can where applicable. Cheers. ![](https://secure.gravatar.com/avatar/7e052c1d09941b211f2012c46fcbc3610c9267358b62320c81aa11d88aac7d54? s=60&d=retro&r=g) ### 󠀁[Helpful](https://wordpress.org/support/topic/helpful-488/)󠁿 [Blucube](https://profiles.wordpress.org/edhicks/) 5 dezembro, 2025 1 resposta By it’s nature this is going to flag false positives – potential issues that you’ve dealt with in different ways, or issues that don’t necessarily apply to your particular case – and it does. But it’s a really useful tool to run a quick check and uncover little omissions or improvements to be made. ![](https://secure.gravatar.com/avatar/98882bbd1717ececb0fb9acab6f8a015b9323eb670fb2f309fb1d5e5cfdb04b9? s=60&d=retro&r=g) ### 󠀁[Simple and effective tool for quick plugin checks](https://wordpress.org/support/topic/simple-and-effective-tool-for-quick-plugin-checks/)󠁿 [Mohammed Kateregga](https://profiles.wordpress.org/mohkatz/) 29 julho, 2025 1 resposta Simple and effective plugin check tool, there is room for improvement and adding more functionality with AI, but overall it currently still gets the job done. [ Leia todas as 32 avaliações ](https://wordpress.org/support/plugin/plugin-check/reviews/) ## Colaboradores e desenvolvedores “Plugin Check (PCP)” é um programa de código aberto. As seguintes pessoas contribuíram para este plugin. Colaboradores * [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/) Plugin Check (PCP)” foi traduzido para 15 localidades. Agradecemos aos [tradutores](https://translate.wordpress.org/projects/wp-plugins/plugin-check/contributors) por suas contribuições. [Traduzir o “Plugin Check (PCP)” para seu idioma.](https://translate.wordpress.org/projects/wp-plugins/plugin-check) ### Interessado no desenvolvimento? [Navegue pelo código](https://plugins.trac.wordpress.org/browser/plugin-check/), consulte o [repositório SVN](https://plugins.svn.wordpress.org/plugin-check/) ou assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/plugin-check/) por [RSS](https://plugins.trac.wordpress.org/log/plugin-check/?limit=100&mode=stop_on_copy&format=rss). ## Registro de alterações #### 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` apiVersion` 3+ 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. #### 1.6.0 * Enhancement – Support strict output format for CLI commands. * Enhancement – Improve check for donate link in readme. * Enhancement – Improve info check in Version utils. * Enhancement – Improve URL validation for plugin header fields. * Enhancement – Improve ruleset files. * Enhancement – Increased severity for invalid plugin uri domain and plugin description checks in plugin header. * Enhancement – Remove CallTimePassByReference as it’s deprecated rule. * Enhancement – Disallow special characters in textdomain. * Enhancement – Imported readme parser for preventing conflicts with wordpress. org. Use dotorg readme parser if available. * Enhancement – Discourage the use of `load_plugin_textdomain` found in plugins as it’s not necessary in wordpress.org. * Enhancement – Upgrade severity for missing readme headers. * Enhancement – Show tested up to minor check only when it is current major version. * Enhancement – Added link in plugins page to run the plugin check. * Fix – Dynamic WP Content folder. * Fix – Fix test for special chars in file names giving problems to users after clone. * Fix – Remove Image_Functions_Check as they were making false positives. * Fix – Prevent WordPress version 10+ from being flagged as an error in the “Tested up to” check. #### 1.5.0 * Enhancement – Improve url validation to check duplicate protocol. * Enhancement – Update severity for incorrect textdomains and i18n error codes. * Enhancement – Now issues in URL Author check are ERROR instead of WARNING. * Enhancement – New check for minor version in Tested up. * Enhancement – Make sure headers are not empty in the requires header check. * Enhancement – Include experimental option in admin. * Enhancement – Add Behat test for experimental checks from addons. * Enhancement – Improve license check for Apache. * Enhancement – Warn if requires headers are not same in readme and plugin header. * Fix – Remove warning for dynamic callback in register_setting check. * Fix – Incorrect database tables being referenced on subsites in Multisite. #### 1.4.0 * Enhancement – Allow ISC license in the License check. * Enhancement – Added check for use of settings with sanitization callback. * Enhancement – Added –ignore-codes in CLI to introduce a mechanism to ignore specific error codes. * Enhancement – New utils for fetching necessary version info details. * Enhancement – Added check for unsupported plugin name in plugin header field. * Enhancement – Segregate the severity of i18n checks. Make sure that is giving errors in the right context. * Enhancement – Provide more detailed information about checks when the README does not include a tested version or a list of contributors. * Enhancement – Added rules from WPCS to prevent issues with content being sent before headers and warn about the use of Call-time pass-by-reference. * Enhancement – Give more context in the error of check wrong named files. * Enhancement – Simplified PHPUnit setup. Now it does not depend of running inside a WordPress installation. * Enhancement – Added new check for restricted contributors. * Fix – Delete transients in unit tests to avoid false positives. * Fix – Incorrect Tested up to version comparison will make error for two major versions up. * Fix – Excluded the use of functions file_get_contents and file_put_contents in the check to prevent false positives. * Fix – Duplicated error message in the check for wrong named files. * Fix – Use of Json encode wasn’t firing the error message. * Fix – Change error type of NonEnqueuedImage in ImageFunctions sniff from ERROR to WARNING. #### 1.3.1 * Enhancement – Add version utilities. * Fix – Escape error messages. * Fix – Renamed error type to ERROR_LOW_SEVERITY and WARNING_LOW_SEVERITY. * Fix – Fix PHPCS checks on unwritable filesystems. #### 1.3.0 * Enhancement – Update disallowed domains for Plugin URI check. * Enhancement – Added new checks for Plugin Header fields: missing plugin description, missing plugin version and invalid plugin version. * Enhancement – New check for validation of donate link in the readme file. * Enhancement – Increased severity for wrong Plugin Requires. * Enhancement – Added check Restrict parse_str() without second argument. * Enhancement – New check for Disallow usage of HEREDOC and NOWDOC. * Enhancement – Added acronyms allowed in Trademark checks. * Enhancement – Added option in CLI to add low severity errors and warnings. * Enhancement – Change error type for License check error codes. * Enhancement – Always use prefixed tables during runtime check requests. * Enhancement – Created a new class for checking licenses. * Enhancement – Added support for MPL-2.0 license. * Enhancement – Implement gherkin linter in GH action. * Enhancement – Update check for Contributors in markdown readme files. * Enhancement – CLI: Fix confusing runtime environment setup order. * Enhancement – Allow custom checks to provide installed_paths. * Enhancement – Improved the use of localhost URLs in the Plugin. * Enhancement – Documented checks in the plugin. * Enhancement – Increased severity for Code obfuscation checks. * Enhancement – Differentiate between non-existent readme and default readme file. * Enhancement – Encourage developers to use native functions for loading images in templates. * Enhancement – Added a check for not allowing include libraries already in WordPress core. * Enhancement – Warning for usage of query_posts() in favor of WP_Query. * Fix – Fix for the local environment is set up before testing. * Fix – Fix addon checks not being executed when running runtime checks. * Fix – Allow `default` as a text domain in the text domain check. * Fix – Allow GitHub URLs in the Plugin URI field. * Fix – Don’t flag Apache license. It’s allowed in the WordPress.org plugin repository. * Fix – Removes the path before the plugin, so it won’t affect to badly named files. #### 1.2.0 * Enhancement – Added a check for badly used names in files. * Enhancement – Increased severity for `BacktickOperator`, `DisallowShortOpenTag`,` DisallowAlternativePHPTags`, `RestrictedClasses`, and `RestrictedFunctions`. * Enhancement – Added security checks to the Plugin repository category. * Enhancement – Allowed `runtime-set` in code sniffer checks. * Enhancement – Changed warnings to errors in plugin header checks. * Enhancement – Detect forbidden plugin headers such as repository URIs in the Directory. * Enhancement – Added a new check for development functions that are not allowed in final plugins. * Enhancement – Created new images and icons for the plugin. * Enhancement – Introduced a slug argument in the CLI. * Enhancement – Added a check for discouraged PHP functions. * Enhancement – Added validation for Contributors in the readme file. * Enhancement – Added a warning for mismatched plugin names in the plugin header and readme file. * Enhancement – Checked for validation of Plugin Header fields: Name, Plugin URI, Description, Author URI, Requires at least, Requires PHP, and Requires Plugins. * Enhancement – Added a warning if the “Tested up to” value in the readme file exceeds the released version of WordPress. * Fix – Display a success message if no errors or warnings are found. * Fix – Made table results responsive. * Fix – Prevent proceeding to the next check if the Stable Tag value is set to ` trunk`. * Fix – Allow runtime initialization even when only add-on checks are requested. * Fix – Fixed an SPDX warning for the `GPL version 3` license. * Fix – Prevent runtime checks in the CLI context when they cannot be used. #### 1.1.0 * Feature – New `Non_Blocking_Scripts_Check` (`non_blocking_scripts`) runtime check to warn about enqueued scripts that use neither `defer` nor `async`. * Enhancement – Changed the namespace of included checks. * Enhancement – Introduced severity levels for all errors and warnings. * Enhancement – CLI: Support checking a plugin from a path or URL. * Enhancement – Added short descriptions and URLs for each check. * Enhancement – Improved messaging in check results. * Enhancement – Updated code obfuscation check with more accurate results. * Enhancement – Updated plugin review check to flag missing input sanitization (` WordPress.Security.ValidatedSanitizedInput`). * Fix – Improve readme checks to exclude invalid files. * Fix – Only show edit link if files are actually editable. #### 1.0.2 * Feature – New `Enqueued_Scripts_Scope_Check` (`enqueued_scripts_scope`), `Enqueued_Styles_Size_Check`(` enqueued_styles_size`) and `Enqueued_Resources_Check` (`enqueued_resources`) performance checks. * Enhancement – Improved readme check and added a new `wp_plugin_check_ignored_readme_warnings` filter. * Enhancement – New `wp_plugin_check_default_categories` filter to change the categories which are selected by default. * Enhancement – New `wp_plugin_check_ignore_files` filter to allow ignoring specific files. * Fix – Correct detection of readme files in Windows by normalizing file paths. #### 1.0.1 * Fix – Add missing `test-content` folder needed for runtime checks. * Fix – Do not send emails when setting up test environment. * Fix – Prevent PHP warning when the `argv` variable isn’t set. #### 1.0.0 * Feature – Complete overhaul of the plugin, its architecture, and all checks. * Feature – Added new [WP-CLI commands](https://github.com/WordPress/plugin-check/blob/trunk/docs/CLI.md) for running checks and listing available options. * Enhancement – Added option to only run checks for a specific category. #### 0.2.3 * Tweak – Use version [3.8.0 of the PHP_CodeSniffer](https://github.com/PHPCSStandards/PHP_CodeSniffer/releases/tag/3.8.0) library, moving away from `squizlabs/PHP_CodeSniffer` to use `PHPCSStandards/ PHP_CodeSniffer`. * Fix – Ensure the plugin works as expected on the WP playground environment to enable reviewers to use PCP. Props @tellyworth. * Fix – Undefined array key “argv” when running the plugin check in certain environments. Props @afragen. [#340](https://github.com/WordPress/plugin-check/pull/340) #### 0.2.2 * Enhancement – Include support for Windows Servers. * Enhancement – Avoid using PHP CLI directly, which enables plugin developers to use PCP in a variety of new environments. * Fix – Remove dependency on `shell_exec` and `exec` functions, which enables plugin developers to use PCP in a variety of new environments. * Fix – Prevent problems with Readme parser warning related to `contributor_ignored` for when running the check outside WP.org. Props @dev4press. [#276](https://github.com/10up/plugin-check/pull/276) * Fix – Remove extra period on the end of the sentence for Phar warning. Props @pixolin. [#275](https://github.com/10up/plugin-check/pull/275) #### 0.2.1 * Added – ‘View in code editor’ link beneath each PHPCS error or warning. Props @EvanHerman, @westonruter, @felixarntz, @mukeshpanchal27 [#262](https://github.com/10up/plugin-check/pull/262) * Fix – Ensure `readme.txt` has priority over `readme.md` when both are present. Props @bordoni, @afragen [#258](https://github.com/10up/plugin-check/pull/258) * Fix – Ensure that the PHPCS check runs even when the PHPCS binary is not executable. Props @bordoni, @shawn-digitalpoint, @mrfoxtalbot [#254](https://github.com/10up/plugin-check/pull/254) * Fix – Readme changes and typos. Props @aaronjorbin. [#261](https://github.com/10up/plugin-check/pull/261) * Fix – Long lines of code with PHPCS check no longer expand over the size of the notice. Props @bordoni, @felixarntz. [#263](https://github.com/10up/plugin-check/pull/263) * Fix – Ensure that we have PHP 7.2 compatibility remove trailing comma. Props @bordoni, @leoloso. [#265](https://github.com/10up/plugin-check/issues/265) * Fix – Include all strings that were missed in the previous release. Props @bordoni, @pixolin. [#270](https://github.com/10up/plugin-check/issues/270) #### 0.2.0 * Feature – Enable modification of the PHP Binary path used by the plugin with ` PLUGIN_CHECK_PHP_BIN` constant. * Feature – Include a check for the usage of `ALLOW_UNFILTERED_UPLOADS` on any PHP files – Props EvanHerman at [#45](https://github.com/WordPress/plugin-check/pull/45) * Feature – Include a check for the presence of the application files (`.a`, `. bin`, `.bpk`, `.deploy`, `.dist`, `.distz`, `.dmg`, `.dms`, `.DS_Store`, `.dump`,`. elc`, `.exe`, `.iso`, `.lha`, `.lrf`, `.lzh`, `.o`, `.obj`, `.phar`, `.pkg`, `. sh`, ‘.so`) – Props EvanHerman at [#43](https://github.com/WordPress/plugin-check/pull/43) * Feature – Include a check for the presence of the readme.txt or readme.md file– Props EvanHerman at [#42](https://github.com/WordPress/plugin-check/pull/42) * Fix – Ensure that Readme parsing is included properly when a readme.md or readme. txt file is present. Props Bordoni [#52](https://github.com/WordPress/plugin-check/pull/52) * Tweak – Disallow functions `move_uploaded_file`, `passthru`, `proc_open` – Props alexsanford at [#50](https://github.com/WordPress/plugin-check/pull/50) * Tweak – Change the message type for using functions WordPress already includes from Warning to Error. Props davidperezgar at [#18](https://github.com/WordPress/plugin-check/issues/18) * Tweak – Change the message type for incorrect usage of Stable tag from Notice/ Warning to Error. Props davidperezgar at [#3](https://github.com/WordPress/plugin-check/issues/3) #### [0.1] 2011-09-04 Original version of the plugin check tool, not a released version of the plugin, this changelog is here for historical purposes only. ## Plugin da comunidade Este plugin é desenvolvido e mantido por uma comunidade. [Contribua com este plugin](https://github.com/WordPress/plugin-check/) ## Meta * Versão **1.9.0** * Última atualização **4 semanas atrás** * Instalações ativas **8.000+** * Versão do WordPress ** 6.3 ou superior ** * Testado até **7.0** * Versão do PHP ** 7.4 ou superior ** * Idiomas * [Catalan](https://ca.wordpress.org/plugins/plugin-check/), [Chinese (Taiwan)](https://tw.wordpress.org/plugins/plugin-check/), [Dutch](https://nl.wordpress.org/plugins/plugin-check/), [English (Australia)](https://en-au.wordpress.org/plugins/plugin-check/), [English (US)](https://wordpress.org/plugins/plugin-check/), [French (France)](https://fr.wordpress.org/plugins/plugin-check/), [German](https://de.wordpress.org/plugins/plugin-check/), [Italian](https://it.wordpress.org/plugins/plugin-check/), [Japanese](https://ja.wordpress.org/plugins/plugin-check/), [Persian](https://fa.wordpress.org/plugins/plugin-check/), [Polish](https://pl.wordpress.org/plugins/plugin-check/), [Portuguese (Brazil)](https://br.wordpress.org/plugins/plugin-check/), [Russian](https://ru.wordpress.org/plugins/plugin-check/), [Spanish (Chile)](https://cl.wordpress.org/plugins/plugin-check/), [Spanish (Spain)](https://es.wordpress.org/plugins/plugin-check/) e [Swedish](https://sv.wordpress.org/plugins/plugin-check/). * [Traduzir para seu idioma](https://translate.wordpress.org/projects/wp-plugins/plugin-check) * Tags * [accessibility](https://br.wordpress.org/plugins/tags/accessibility/)[performance](https://br.wordpress.org/plugins/tags/performance/) [security](https://br.wordpress.org/plugins/tags/security/)[testing](https://br.wordpress.org/plugins/tags/testing/) * [Visualização avançada](https://br.wordpress.org/plugins/plugin-check/advanced/) ## Classificações 4.4 de 5 estrelas. * [ 25 avaliações com 5 estrelas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=5) * [ 1 avaliação com 4 estrela ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=4) * [ 2 avaliações com 3 estrelas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=3) * [ 2 avaliações com 2 estrelas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=2) * [ 2 avaliações com 1 estrelas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/plugin-check/reviews/#new-post) [Ver todas avaliações](https://wordpress.org/support/plugin/plugin-check/reviews/) ## Colaboradores * [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/) ## Suporte Problemas resolvidos nos últimos dois meses: 0 de 1 [Ver fórum de suporte](https://wordpress.org/support/plugin/plugin-check/)