| 开发者 | creatools |
|---|---|
| 更新时间 | 2026年10月14日 10:26 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. It only researches and organizes information for maintenance decisions. WordPress's standard update mechanism remains responsible for updates and automatic-update preferences.
No. Available compatibility and vulnerability information cannot establish complete compatibility or safety. An update candidate still needs your normal testing and maintenance preparation.
Both external research services are opt-in. You choose each service in Settings after reviewing its purpose and transmitted data. Opening the page or activating this plugin does not start its external research requests.
WordPress.org receives a plugin or theme slug and API action, locale and field-selection parameters. Eligible local plugin slug candidates may be queried to verify directory identity; local header names and publisher information are compared locally, not transmitted. WPVulnerability receives a core version or a verified plugin or theme slug. Plugin and theme installed/target versions are matched locally. Both services receive a fixed plugin User-Agent containing this plugin's version and can see the connection IP. See External services below. No site content, site URL, user data, email addresses, passwords, authentication credentials or database content is sent by this plugin's research requests. WordPress itself and other plugins can make their own requests independently.
Available native target requirements can be used with their provenance retained. Directory metadata and vulnerability coverage may be unavailable if identity cannot be verified. An external update source does not by itself rule out a directory identity. Check missing information with the product provider.
No. The current version does not use an AI service.
No. It only changes the value used for assessment. Manual mode remains selected until you explicitly switch back to automatic mode.
The affected information remains incomplete, and other research items can continue. Successful cached data is not overwritten by a request failure. Old negative results cannot establish an update candidate; retained positive findings keep their original retrieval dates.
No. Normal research uses valid caches. Security data has a 6-hour freshness window and directory data a 12-hour window; successful results can be retained for up to 72 hours. Refetching respects consent and service rate limits. Closing the browser stops research; there is no scheduled background monitoring.
Settings, temporary source facts, research snapshots, progress and short-lived coordination data are stored in WordPress. Clear research cache removes tracked research caches; deactivation also clears them while retaining settings. Uninstall removes this plugin's settings, tracked caches, progress and coordination data. WordPress's own update information is not removed.