f(x) TOC
Limited data: f(x) TOC has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Capped at 39: a vulnerability has no patch.
| Ownership | 100 |
|---|---|
| Maintenance | 0 |
| Security | 40 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is f(x) TOC still maintained?
- No. Last release 1 Aug 2016, over 10 years ago. 1 Aug 2016 · wordpress.org
- Who owns f(x) TOC, and has it changed hands?
- No change recorded. 4 Nov 2026 · SVN log
- Was f(x) TOC removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is f(x) TOC safe?
- No. 1 known vulnerability has no fix in the current version. 18 Apr 2023 · Wordfence Intelligence
- Is the latest f(x) TOC update safe to install?
- No ownership change before 1.1.0. No one-star spike after it. 4 May 2016 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 18 Apr 2023 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.2 May 2023Evidence
- CriticalMNT-1No release in 124 months (last release 1 Aug 2016). Plan a replacement if the plugin is important to your site.1 Aug 2017Evidence
- WarningMNT-2Tested up to WordPress 4.7.39, 24 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
No ownership change since 2016.
Maintenance
- Last release
- 10 years ago
- Releases, 24 months
- 0
- Tested up to
- 4.7 vs 7.1
- Requires PHP
- not stated 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 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 1 Aug 2016. Tested up to 4.7, 24 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 5.0.
| 5 star | 5 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 0 |
Security record
1 vulnerability on record, 1 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 18 Apr 2023 | f(x) TOC <= 1.1.0 - Authenticated (Contributor+) Stored Cross-Site Scripting | 6.4 | <= 1.1.0 | No fix | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
200+ active installs. History builds with each weekly snapshot.
Momentum history builds with each snapshot.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
No healthier plugin in the same category yet.
Facts
| Version | 1.1.0 |
|---|---|
| Author | David Chandra Purnama |
| Added | 25 Feb 2016 |
| Last updated | 1 Aug 2016 |
| Active installs | 200+ |
| Requires WordPress | 4.0 |
| Tested up to | 4.7.39 |
| Requires PHP | not stated |
| Category | not stated |
| Tags | toc, heading, shortcode, toc shortcode, table of contents |
Other plugins by this author: f(x) Editor, f(x) Email Log, f(x) Skype Link Enabler, f(x) Login Notification, f(x) SSL, f(x) Categories Widget, f(x) Login Customizer, f(x) Profile Dashboard Widget, f(x) Builder, f(x) Photo Tag, f(x) Share, f(x) SEO
Questions
Is f(x) TOC still maintained?
No. Last release 1 Aug 2016, over 10 years ago.
Who owns f(x) TOC, and has it changed hands?
No change recorded.
Was f(x) TOC removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is f(x) TOC safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest f(x) TOC update safe to install?
No ownership change before 1.1.0. No one-star spike after it.