| 开发者 | oopspam |
|---|---|
| 更新时间 | 2026年4月16日 15:22 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
oop-vulns folder to the /wp-content/plugins/ directoryYes, an API key is required to check for vulnerabilities. Each API key includes 40 vulnerability checks per month. Each plugin or theme check counts as one API call. If you're using the OOPSpam Anti-Spam plugin, the API key is shared automatically.
Each vulnerability check for a plugin or theme counts as one API call. For example, if you have 20 plugins and 5 themes, a full scan uses 25 API calls (plus 1 for WordPress core).
Scanning is disabled by default. After you explicitly enable scanning, you can configure scans to run daily or weekly and run manual scans from the dashboard.
Only plugin/theme slugs and version numbers are sent. No personal data, content, or sensitive information is transmitted.
No. Scans run in the background via WordPress cron and results are cached. The plugin does not affect frontend performance.
Yes. You can enter your API key in the plugin settings, or define OOPSPAM_API_KEY in your wp-config.php file.