Plugin profile · observed daily since 02 Aug 2026
Time since 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 freanki 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 |
|---|---|---|---|
| freanki | 2 | 03 Apr 2012 | 03 Apr 2012 |
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: 10+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
0 downloads a day over the last 7 days, steady 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.
Unchanged throughout: downloads that day (0) · ratings total (0) · active installs (10+) · version (0.6) · support threads (0) · threads resolved (0)
38 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?
- No release in 5,271 days (14.4 years). The last was 03 Apr 2012.
- Declares compatibility only up to WordPress 3.3.2, while 7.1 is current. The author has not confirmed it runs on the last 38 releases.
- freanki publishes no other plugin in the directory, so there is no wider activity to compare against.
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.
- 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.
- 25 Sep 201312 years agoDormancy threshold crossed540 days since the last release (2012-04-03). Dormancy is a maintenance observation, not a judgement about the owner.
- 03 Apr 201214 years agoVersion 0.6 released
- 03 Apr 201214 years agoVersion 2.0 releasedfrom the release logCommitted by freanki.
- 02 Apr 201214 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 freanki for all 38 days we have observed it.
- It was last released 14 years ago (03 Apr 2012).
- Its author declares it tested up to WordPress 3.3.2; WordPress is now on 7.1.
- WordPress.org reports 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.
Automatically change your post date display to "time ago" format like 1 hour ago, 3 days ago, etc...
Shortcode to show any current, past, and future date or time. Display this, previous, or next year, month, day, etc.
A date-time add-on for Gravity Forms with custom date time format.
This plugin provides Erisian (Discordian) dates and time in Wordpress. Also provides shortcode and widget which displays the clock, current date accor …
Shortcodes to wrap around text, which specify at what date or time that content should appear or disappear, either once, or on a recurring basis.
This plugin shows the server local current date time & timezone in the upper right of your admin screen on every page.
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 Time since date: a person reads every submission, and corrections get a reply within 5 business days.