Plugin profile · observed daily since 02 Aug 2026
Pointwise Summary – AI-Powered TLDR, AI Summarize & Social Sharing
Active installsfewer than 10 rounded
Current authorAllyWorker
Owner changesNone while we have been watching
Last releaseyesterday 29 Aug 2026
Support— no recent threads
Releases on record8
Rating— no ratings yet
Added to directory07 May 2026
Requires WP6.1
Requires PHP7.4
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
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
28 Aug 2026
Owner display name changed
“Aminul Islam” → “AllyWorker”. The wordpress.org account is unchanged, so this is the same owner relabelling themselves, not a transfer. Recorded as a fact; it carries no score weight.
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 |
|---|---|---|---|
| theaminuldev | 7 | 07 May 2026 | 28 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.
9 downloads a day over the last 7 days, rising 464% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
10 Aug 2026peak 41/day30 Aug 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 | 17 Aug | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 21 | 41 |
| Version | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.2 | 1.2.3 | 1.2.3 | 1.2.4 |
Unchanged throughout: ratings total (0) · active installs (0+) · support threads (0) · threads resolved (0)
23 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 directory4 months ago 07 May 2026
Requires WP6.1
Requires PHP7.4
Version lagcurrent
Is anyone still maintaining this?
- Last released 29 Aug 2026, 1 days ago.
- Declares compatibility with WordPress 7.1, which is current.
- The same account maintains 3 other plugins, 3 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.
- 29 Aug 2026yesterdayVersion 1.2.4 released
- 28 Aug 20262 days agoVersion 1.2.3 released
- 28 Aug 20262 days agoOwner display name changed“Aminul Islam” → “AllyWorker”. The wordpress.org account is unchanged, so this is the same owner relabelling themselves, not a transfer. Recorded as a fact; it carries no score weight.
- 07 Aug 202623 days agoVersion 1.2.2 released
- 02 Aug 202628 days agoVersion 1.2.1 releasedfrom the release logCommitted by theaminuldev.
- 02 Aug 202628 days 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.
- 22 Jun 20262 months agoVersion 1.2.0 released
- 13 May 20264 months agoVersion 1.1.0 releasedfrom the release logCommitted by theaminuldev.
- 10 May 20264 months agoVersion 1.0.0 releasedfrom the release logCommitted by theaminuldev.
- 07 May 20264 months agoVersion 0.5.0 releasedfrom the release logCommitted by theaminuldev.
- 07 May 20264 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 AllyWorker for all 23 days we have observed it.
- It was last released yesterday (29 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.
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
Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.
Sumtics – AI Summarizer & TL;DR Generator
AI summarizer for WordPress. Auto-generate TL;DR summaries on your posts and add one-click ChatGPT, Claude, Gemini & Perplexity summarize buttons.
50+ installsupdated 23 Jun 2026
Compare side by side SoftWin AI Summarize
Adds a configurable AI summary widget before standard WordPress post content.
fewer than 10 installsupdated 22 Jun 2026
Compare side by side AI Post Summarizer Lite for WordPress
Add an instant AI button to summarize WordPress posts. Provide a quick TLDR for readers. No API key needed. 100% free. Works with ChatGPT & Google AI.
fewer than 10 installsupdated 23 May 2026
Compare side by side Auto Summarize Post Content
Auto-summarize content and display it at the top or bottom of the post.
100+ installs3.0★ (2)updated 27 Sep 2024
no release in over 18 months
Compare side by side AIRize: Content summarize with AI
Adds AI summary buttons that open ChatGPT, Gemini, Perplexity, or Grok to summarize the current page.
fewer than 10 installsupdated 27 Dec 2025
Compare side by side Bix AI Writer
AI-assisted content & summary generator for the WordPress block editor. Works with OpenAI, OpenRouter, or local Ollama. No vendor lock-in.
10+ installsupdated 17 Oct 2025
Compare side by side 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 Pointwise Summary – AI-Powered TLDR, AI Summarize & Social Sharing: a person reads every submission, and corrections get a reply within 5 business days.