Is Simple Custom CSS Plugin still maintained?
Not visibly. The WordPress.org directory shows the last release of Simple Custom CSS Plugin 19 months ago. A year's silence is a signal rather than a verdict, and it is worth knowing about before your next WordPress or PHP upgrade.
The evidence
Every figure below is read from the WordPress.org plugin directory. Nothing here is our assessment of the code.
| Last release | 11 March 2025 (19 months ago) |
|---|---|
| Current version | 4.0.7 |
| Tested up to | WordPress 6.7.10 (current is 7.1.3, 4 releases ahead) |
| Active installs | At least 100,000 sites (the directory reports a rounded floor, not an exact count) |
| Support threads | No threads in the last two months |
| Directory status | Listed |
| Read from the directory | 21 October 2026 |
What these signals mean
A year without a release is a signal rather than a verdict. Plenty of narrow plugins genuinely need no changes for a year, and WordPress is unusually careful about backwards compatibility, so nothing has necessarily gone wrong.
What it changes is who fixes it if something does. A maintained plugin is one where a breaking change in PHP or WordPress core produces a release; an unmaintained one is where it produces a support thread nobody answers. Treat the gap as a reason to know what you would move to, not as a reason to move today.
What to do about it
Nothing urgent. Note it, and know what you would replace it with, so that the decision is already made if a PHP or WordPress upgrade breaks something.
The moment to act is before an upgrade rather than after one. If you are planning a PHP version bump or a major WordPress release, test this plugin on a staging copy first, because if its author has moved on, nobody else is going to fix it for you.
Is a site you look after running Simple Custom CSS Plugin?
Our free WordPress plugin checker reads any public site and lists the plugins it loads, with the same maintenance signals as the table above for each one. No login and no signup, so it works on a client’s site before you have access to it.
Maintained alternatives
From the same category in the WordPress.org directory, filtered to plugins that have shipped a release in the last year and are installed on at least 10,000 sites. Chosen by those rules rather than by us, and worth checking against the same signals before you commit to one.
- WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager at least 3 million sites, last updated 8 October 2026 See its maintenance signals
- Code Snippets at least 1 million sites, last updated 20 October 2026 See its maintenance signals
- Head & Footer Code at least 100,000 sites, last updated 31 August 2026
Related plugin checks
- Is Safe SVG still maintained? Updated 22 September 2026, current against recent WordPress. Nothing of concern.
- Is Classic Editor still maintained? Updated 28 May 2026, current against recent WordPress. Nothing of concern.
- Is Classic Widgets still maintained? Released 8 December 2025, tested up to WordPress 6.9.10, 2 releases behind.
- Is Advanced Custom Fields still maintained? Updated 10 September 2026, current against recent WordPress. Nothing of concern.
- Is Custom Post Type UI still maintained? Updated 14 July 2026, current against recent WordPress. Nothing of concern.
Related links
- Which WordPress plugins are still maintained? Every plugin we check, with its last release.
- Custom WordPress plugin development When Simple Custom CSS Plugin has to be replaced or taken over and nothing in the directory fits.
Link to this check
Maintain Simple Custom CSS Plugin, or write about it? This badge links to this page, so your readers can see the same evidence. Copy the HTML below.
<a href="https://zignites.com/plugin-check/simple-custom-css"><img src="https://zignites.com/badges/plugin-checker.svg" alt="Maintenance signals for Simple Custom CSS Plugin, checked with Zignites Plugin Checker" width="232" height="20"></a>Questions
When was Simple Custom CSS Plugin last updated?
The WordPress.org directory records its most recent release as 11 March 2025, which is 19 months ago. That date is read from the directory each time this page is built, and the page states when it was read.
Should I remove Simple Custom CSS Plugin from my site?
Not on the strength of the date alone. 19 months without a release is a reason to know what you would replace it with, not a reason to replace it today. The moment that matters is a PHP or WordPress upgrade, because that is when a plugin without an active author breaks with nobody there to fix it.
Is Simple Custom CSS Plugin a security risk?
We do not know, and nothing on this page is a security finding. Vulnerability data for WordPress plugins sits behind paid commercial APIs, and guessing at it from a version number either alarms people about plugins that are fine or implies that everything unflagged has been checked and is safe. Both are worse than saying nothing. What this page reports is maintenance: when the plugin last shipped, which WordPress version its author last tested against, and whether the directory still lists it. Those are facts the directory publishes, and they are what predicts whether a plugin will still work after the next core release.
Read from the WordPress.org plugin directory on 21 October 2026. We report maintenance signals only, and never claim a plugin is insecure. All plugins we cover.