Plugin profile · observed daily since 02 Aug 2026
Chiramise
PluginsPedia 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 Hametuha INC. since 15 Oct 2026, when it last changed hands. 1 ownership change on record since daily tracking began on 02 Aug 2026.
We track the wordpress.org account behind each plugin. An owner renaming themselves is recorded as a rename, never as a transfer. How ownership changes are detected
Fumiki Takahashi → Hametuha INC.. 3 plugins moved between the same two accounts between 01 Oct 2026 and 15 Oct 2026.
Plugins in the same group: hamecache, wp-yomigana
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 |
|---|---|---|---|
| Takahashi_Fumiki | 5 | 09 Nov 2016 | 30 May 2019 |
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.
3 downloads a day over the last 7 days, falling 63% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
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 | 18 Oct | 19 Oct | 20 Oct | 21 Oct | 22 Oct | 23 Oct | 24 Oct | 25 Oct | 26 Oct | 27 Oct | 28 Oct | 29 Oct | 30 Oct | 31 Oct |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 36 | 11 | 0 | 13 | 11 | 0 | 0 | 0 | 11 | 0 | 0 |
| Version | 1.1.2 | 1.1.2 | 1.1.2 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 |
Unchanged throughout: ratings total (0) · active installs (0+) · support threads (0) · threads resolved (0)
91 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 20 Oct 2026, 20 days ago.
- Declares compatibility with WordPress 7.1.4, which is current.
- The same account maintains 5 other plugins, 5 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.
- 20 Oct 202620 days agoVersion 1.1.3 released
- 20 Oct 202620 days agoReleased after a long silenceA new release arrived 2,700 days after the previous one (2019-05-30). A break in dormancy is a maintenance observation, not a judgement about the release or the owner.
- 15 Oct 202625 days agoCustody change, one of 3 pluginsFumiki Takahashi → Hametuha INC.. 3 plugins moved between the same two accounts between 01 Oct 2026 and 15 Oct 2026.
- 02 Aug 20263 months agoFirst observed by PluginsPediaDaily 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.
- 20 Nov 20205.5 years agoDormancy threshold crossed540 days since the last release (2019-05-30). Dormancy is a maintenance observation, not a judgement about the owner.
- 30 May 20197 years agoVersion 1.1.2 released
- 30 May 20197 years agoVersion 1.1.1 releasedfrom the release logCommitted by Takahashi_Fumiki.
- 27 May 20197 years agoVersion 1.1.0 releasedfrom the release logCommitted by Takahashi_Fumiki.
- 18 Nov 20169.5 years agoVersion 1.0.1 releasedfrom the release logCommitted by Takahashi_Fumiki.
- 09 Nov 20169.5 years agoVersion 1.0.0 releasedfrom the release logCommitted by Takahashi_Fumiki.
- 09 Nov 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
- The wordpress.org account holding it changed once on 15 Oct 2026, to Hametuha INC..
- 3 plugins moved between the same two accounts in the same window.
- It was last released 20 days ago (20 Oct 2026).
- Its author declares it tested up to WordPress 7.1.4, 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.
Membership & community plugin with user profiles, registration & login, member directories, content restriction, user roles and much more.
Paid membership & LMS plugin. Sell courses, subscriptions & digital products, paywall content, and add login & registration forms and user profiles.
Build membership sites with tiered plans, content restriction, drag-&-drop custom registration & login form builder, and built-in payment system.
The original WordPress membership plugin with content restriction, user login, custom registration fields, user profiles, and more.
Build your email subscriber lists, send email marketing newsletters, create landing pages, build custom subscription forms with the Form Builder block …
Simple membership plugin adds membership functionality to your site. Protect members only content using content protection easily.
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 Chiramise: a person reads every submission, and corrections get a reply within 5 business days.