Plugin profile · observed daily since 02 Aug 2026
RoleCraft: User Access Control – Roles, Capabilities & Content Restriction
Active installsfewer than 10 rounded
Current authorAngelo Rocha
Owner changesNone while we have been watching
Last release23 days ago 25 Aug 2026
Support— no recent threads
Releases on record10
Rating— no ratings yet
Added to directory08 Oct 2024
Requires WP6.1
Requires PHP8.1
Version lag0 up to date
Tested up toWP 7.1 up to date
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 Angelo Rocha 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 |
|---|---|---|---|
| angelorocha | 10 | 08 Oct 2024 | 25 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.
Very early-stage: fewer than 10 active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
2 downloads a day over the last 7 days, falling 21% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 46/day17 Sep 2026
No ratings on record, so there is no sentiment to report.
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 | 04 Sep | 05 Sep | 06 Sep | 07 Sep | 08 Sep | 09 Sep | 10 Sep | 11 Sep | 12 Sep | 13 Sep | 14 Sep | 15 Sep | 16 Sep | 17 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 0 | 0 | 14 | 0 | 0 | 0 | 0 | 11 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (0+) · version (1.3.0) · support threads (0) · threads resolved (0)
47 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory23 months ago 08 Oct 2024
Requires WP6.1
Requires PHP8.1
Version lagcurrent
Is anyone still maintaining this?
- Last released 25 Aug 2026, 24 days ago.
- Declares compatibility with WordPress 7.1, which is current.
- The same account maintains 1 other plugin, and none has been updated in over a year, the most recent on 27 Oct 2021.
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.
- 25 Aug 202624 days agoVersion 1.3.0 released
- 19 Aug 202630 days agoVersion 1.2.3 released
- 19 Aug 202630 days agoVersion 1.2.2 releasedfrom the release logCommitted by angelorocha.
- 18 Aug 20261 month agoVersion 1.2.1 released
- 15 Aug 20261 month agoVersion 1.2.0 released
- 14 Aug 20261 month agoVersion 1.1.3 released
- 14 Aug 20261 month agoReleased after a long silenceA new release arrived 556 days after the previous one (2025-02-04). A break in dormancy is a maintenance observation, not a judgement about the release or the owner.
- 02 Aug 20262 months 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.
- 29 Jul 20262 months agoDormancy threshold crossed540 days since the last release (2025-02-04). Dormancy is a maintenance observation, not a judgement about the owner.
- 04 Feb 202519 months agoVersion 1.1.2 released
- 11 Oct 202423 months agoVersion 1.1.0 releasedfrom the release logCommitted by angelorocha.
- 11 Oct 202423 months agoVersion 1.1.1 releasedfrom the release logCommitted by angelorocha.
- 08 Oct 202423 months agoVersion 1.0.0 releasedfrom the release logCommitted by angelorocha.
- 08 Oct 202423 months 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 Angelo Rocha for all 47 days we have observed it.
- It was last released 23 days ago (25 Aug 2026).
- Its author declares it tested up to WordPress 7.1, which is current.
- WordPress.org reports fewer than 10 active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- 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.
PublishPress Capabilities: User Role Access Control, Admin Area Permissions
User role editing for WordPress. Manage user roles, control capabilities and permissions, and restrict admin access for any role.
100,000+ installs4.7★ (143)updated 10 Sep 2026
Restrict User Access – Ultimate Membership & Content Protection
Create Access Levels and restrict any post, page, category, etc. Supports bbPress, BuddyPress, WooCommerce, WPML, and more.
10,000+ installs4.3★ (94)updated 27 Aug 2026
RoleMaster Suite – User Role Editor for E-Commerce, Membership & Admin Panel
Create, manage, and assign WordPress user roles and capabilities with precision — ideal for e-commerce and membership sites.
700+ installs3.7★ (3)updated 08 Sep 2026
1 ownership change on record
RoleMatrix
A powerful plugin to manage user roles, capabilities, and admin menu access with advanced URL restrictions.
10+ installsupdated 29 Aug 2026
Members – Membership & User Role Editor Plugin
The best WordPress membership and user role editor plugin. User Roles & Capabilities editor helps you restrict content in just a few clicks.
300,000+ installs4.9★ (1,277)updated 25 Aug 2026
Advanced Access Manager – Access Governance for WordPress
Access Governance for WordPress. Control roles, users, content, admin areas, and APIs to prevent broken access controls and excessive privileges.
100,000+ installs4.2★ (420)updated 08 Sep 2026
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 RoleCraft: User Access Control – Roles, Capabilities & Content Restriction: a person reads every submission, and corrections get a reply within 5 business days.