Plugin profile · observed daily since 02 Aug 2026
SMNTCS Disable REST API User Endpoints
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Niels Lange throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| nielslange | 16 | 20 Feb 2019 | 14 Aug 2026 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Moderately adopted: 8,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
23 downloads a day over the last 7 days, falling 73% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Install band rose to 8,000+ on 16 Aug 2026, from 7,000+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 22 | 35 | 44 | 34 | 0 | 94 | 0 | 46 | 33 | 23 | 23 | 0 | 39 |
Unchanged throughout: ratings total (2) · active installs (8,000+) · version (2.5) · support threads (0) · threads resolved (0)
37 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- Last released 14 Aug 2026, 25 days ago.
- Declares compatibility only up to WordPress 7.0.4, while 7.1 is current. The author has not confirmed it runs on the last 1 release.
- The same account maintains 22 other plugins, 12 of which were updated in the last 90 days. the account is active.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 14 Aug 202625 days agoVersion 2.5 released
- 14 Aug 202625 days agoReleased after a long silenceA new release arrived 591 days after the previous one (2024-12-31). A break in dormancy is a maintenance observation, not a judgement about the release or the owner.
- 02 Aug 20261 month agoInstall band moved to 7,000+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 24 Jun 20262 months agoDormancy threshold crossed540 days since the last release (2024-12-31). Dormancy is a maintenance observation, not a judgement about the owner.
- 31 Dec 202420 months agoVersion 2.4 released
- 19 Oct 202423 months agoVersion 2.3 releasedfrom the release logCommitted by nielslange.
- 15 Oct 20232.5 years agoVersion 2.2 releasedfrom the release logCommitted by nielslange.
- 11 Mar 20233.5 years agoVersion 2.1 releasedfrom the release logCommitted by nielslange.
- 03 Dec 20223.5 years agoVersion 2.0 releasedfrom the release logCommitted by nielslange.
- 09 Jun 20224 years agoVersion 1.9 releasedfrom the release logCommitted by nielslange.
- 31 Dec 20214.5 years agoVersion 1.8 releasedfrom the release logCommitted by nielslange.
- 01 May 20215 years agoVersion 1.7 releasedfrom the release logCommitted by nielslange.
- 08 Jan 20215.5 years agoVersion 1.6 releasedfrom the release logCommitted by nielslange.
- 10 May 20206 years agoVersion 1.4 releasedfrom the release logCommitted by nielslange.
- 10 May 20206 years agoVersion 1.5 releasedfrom the release logCommitted by nielslange.
- 26 Dec 20196.5 years agoVersion 1.3 releasedfrom the release logCommitted by nielslange.
- 05 Apr 20197 years agoVersion 1.2 releasedfrom the release logCommitted by nielslange.
- 20 Feb 20197.5 years ago2 earlier releasesfrom the release logBetween 20 Feb 2019 and 20 Feb 2019. Listed individually in the public release log rather than here.
- 24 Dec 20169.5 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Niels Lange for all 37 days we have observed it.
- It was last released 24 days ago (14 Aug 2026).
- Its author declares it tested up to WordPress 7.0.4; WordPress is now on 7.1.
- WordPress.org reports 8,000+ active installs.
- It carries 2 ratings, averaging 5.0 out of 5.
What we don’t know yet
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.
Secure REST endpoint to publish posts from BabyLoveGrowth.ai backend via API key.
Standalone activity log with a visual Insights dashboard, a filterable log viewer, and a secure REST endpoint for external monitoring tools.
Use WordPress authentication and permissions in external React applications via secure REST API endpoints.
Advanced security suite. Blocks REST API, disables XML-RPC, prevents user enumeration, and secures endpoints.
Manage access to the WordPress REST API by restricting public endpoints, enabling specific route allow-listing, and handling API key authentication.
Connect WordPress to any REST API. Configure endpoints, manage credentials securely, and display data using shortcodes or template functions.
Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about SMNTCS Disable REST API User Endpoints: a person reads every submission, and corrections get a reply within 5 business days.