Plugin profile · observed daily since 02 Aug 2026
Jooosi Fon – Use Custom Fonts, Google Fonts or Adobe Fonts
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 suasgn since 25 Aug 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
Sua → suasgn. 4 plugins moved between the same two accounts on 25 Aug 2026.
Plugins in the same group: jooosi-mail, omni-icon, windpress
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 |
|---|---|---|---|
| rosua | 69 | 15 Jun 2023 | 28 Jul 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: 5,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
142 downloads a day over the last 7 days, falling 25% 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 | 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 | — | 68 | 30 | 965 | 89 | 94 | 47 | 105 | 60 | 141 | 445 | 170 | 37 | 34 |
| Version | 1.0.114 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 | 1.1.3 |
| Support threads | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
Unchanged throughout: ratings total (25) · active installs (5,000+) · 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 02 Sep 2026, 5 days ago.
- Declares compatibility with WordPress 7.1, which is current.
- 0 of 1 support threads answered in the last two months.
- 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.
- 02 Sep 20265 days agoVersion 1.1.3 released
- 26 Aug 202612 days agoVersion 1.1.1 released
- 25 Aug 202613 days agoCustody change, one of 4 pluginsSua → suasgn. 4 plugins moved between the same two accounts on 25 Aug 2026.
- 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.
- 28 Jul 20261 month agoVersion 1.0.114 released
- 17 Mar 20266 months agoVersion 1.0.100 releasedfrom the release logCommitted by rosua.
- 08 Feb 20267 months agoVersion 1.0.99 releasedfrom the release logCommitted by rosua.
- 05 Feb 20267 months agoVersion 1.0.96 releasedfrom the release logCommitted by rosua.
- 05 Feb 20267 months agoVersion 1.0.97 releasedfrom the release logCommitted by rosua.
- 05 Feb 20267 months agoVersion 1.0.98 releasedfrom the release logCommitted by rosua.
- 01 Feb 20267 months agoVersion 1.0.95 releasedfrom the release logCommitted by rosua.
- 25 Jan 20267 months agoVersion 1.0.94 releasedfrom the release logCommitted by rosua.
- 18 Jan 20268 months agoVersion 1.0.93 releasedfrom the release logCommitted by rosua.
- 11 Jan 20268 months agoVersion 1.0.92 releasedfrom the release logCommitted by rosua.
- 06 Jan 20268 months agoVersion 1.0.91 releasedfrom the release logCommitted by rosua.
- 10 Nov 202510 months agoVersion 1.0.89 releasedfrom the release logCommitted by rosua.
- 10 Nov 202510 months agoVersion 1.0.90 releasedfrom the release logCommitted by rosua.
- 15 Jun 20233 years ago56 earlier releasesfrom the release logBetween 15 Jun 2023 and 31 Aug 2025. Listed individually in the public release log rather than here.
- 15 Jun 20233 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 25 Aug 2026, to suasgn.
- 4 plugins moved between the same two accounts in the same window.
- It was last released 5 days ago (02 Sep 2026).
- Its author declares it tested up to WordPress 7.1, which is current.
- WordPress.org reports 5,000+ active installs.
- It carries 25 ratings, averaging 5.0 out of 5.
- 0 of 1 support threads in the last two months are marked resolved.
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.
The #1 fonts plugin for WordPress. 1,400+ Google Fonts, Adobe Fonts and your own font files. Live preview, no code required.
Improve frontend performance by disabling Google Fonts. GDPR and DSGVO friendly.
Custom Fonts is a powerful WordPress plugin that allows you to upload your own custom fonts or choose from a vast collection of Google Fonts, all host …
Upload custom fonts with custom font uploader. Auto converts to woff2 for better performance. Self-hosted, GDPR compliant, and easy custom font plugin
The original Google Fonts self-hosting plugin. Automagically caches your fonts locally — no configuration (or brains) required!
Easily upload and host fonts locally. Avoid external requests to enhance security, privacy, speed, and GDPR compliance.
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 Jooosi Fon – Use Custom Fonts, Google Fonts or Adobe Fonts: a person reads every submission, and corrections get a reply within 5 business days.