Disable AI for Security
Limited data: Disable AI for Security has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Based on 3 of 5 areas
Capped at 95: not enough support or review data for a full score.
| Ownership | 100 |
|---|---|
| Maintenance | 100 |
| Security | 100 |
| Support | No data |
| Reputation | No data |
Active signals
Open issues right now, with links to the source.
No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.
Quick answers
- Is Disable AI for Security still maintained?
- Yes. Last release 12 Oct 2026, 1 release in the last 24 months. 12 Oct 2026 · wordpress.org
- Who owns Disable AI for Security, and has it changed hands?
- No change recorded. Main committer wpchefgadget since Jun 2026. 3 Nov 2026 · SVN log
- Was Disable AI for Security removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is Disable AI for Security safe?
- No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
- Is the latest Disable AI for Security update safe to install?
- No ownership change before 1.3.0. No one-star spike after it. 16 Jun 2026 · Release history
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| plugin-master | 10 Jun 2026 to 10 Jun 2026, 1 commits |
|---|---|
| wpchefgadget | 16 Jun 2026 to 12 Oct 2026, 3 commits |
2 committers recorded. No ownership changes recorded since 2026.
Maintenance
- Last release
- 23 days ago
- Releases, 24 months
- 1
- Tested up to
- 7.1 current
- Requires PHP
- 7.2 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 0 |
| Q4 2025 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 1 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 12 Oct 2026. Tested with WordPress 7.1 (current).
Support
- Resolved, last 2 months
- n/a
- Threads, last 2 months
- 0
Trend appears after 8 weekly snapshots.
Security record
No published vulnerabilities on record for this plugin.
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Reputation
Last 90 days: no reviews.
| 5 star | 0 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 0 |
Momentum
- Active installs
- 100+
Trend appears after 8 weekly snapshots.
Facts
- Version
- 1.3.0
- Author
- WPChef
- Added
- 16 Jun 2026
- Last updated
- 12 Oct 2026
- Active installs
- 100+
- Requires WordPress
- 7.0
- Tested up to
- 7.1.4
- Requires PHP
- 7.2
- Category
- not stated
- Tags
- AI, privacy, security, connectors, disable-ai
Other plugins by this author: Limit Login Attempts Security, Protection Against DDoS, Use InnoDB, WPChef, Integrum Security Scanner
Questions about Disable AI for Security
Is Disable AI for Security still maintained?
Yes. Last release 12 Oct 2026, 1 release in the last 24 months.
Who owns Disable AI for Security, and has it changed hands?
No change recorded. Main committer wpchefgadget since Jun 2026.
Was Disable AI for Security removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is Disable AI for Security safe?
No known vulnerabilities on record.
Is the latest Disable AI for Security update safe to install?
No ownership change before 1.3.0. No one-star spike after it.