This page provides insights into the most recent data update for Obsidian Stats. It covers data freshness, repository clone status, processed datapoints, and errors encountered during the update process.
| Metric | Value |
| Latest pipeline activity | May 25, 2026 at 11:05 AM UTC |
| Latest plugin download snapshot | May 25, 2026 |
| Latest Obsidian release tracked | 1.12.7 on March 23, 2026 |
| Plugin records | 4,471 total (4,209 active, 262 removed)
|
| Theme records | 589 total (528 active, 61 removed)
|
Pipeline Status
| Stage | Freshness | Status |
| Community plugin dataset | May 25, 2026 | 4,471 plugins and 60,065 version snapshots processed |
| Repository cloning | May 25, 2026 at 11:05 AM UTC | 4,148 current tag checkouts, 16 failed, 262 removed skipped |
| Plugin releases | May 25, 2026 at 11:05 AM UTC | 4,199 successful main.js acquisitions (97.9%) |
| Repository analysis | May 25, 2026 at 11:05 AM UTC | 4,198 active plugins analyzed, 11 misses |
| Obsidian releases | May 25, 2026 at 10:52 AM UTC | 168 GitHub releases, 453 changelog
entries |
Pipeline Errors
- 16 repo clone failures: duplicate-line, vim-toggle, hackerone, tasks-calendar-wrapper, mapbox-location.
- 11 active plugins did not produce repo analysis data, including bojubot, book-tracker, bujuan, cevent-planner, cevent-planner-extra.
- 5 plugin release checks ended in an error or rate-limit state.
Repository Clone Status
This table breaks down local plugin repository checkouts. Active plugin repositories are shallow cloned at the latest known plugin version tag, and an
existing checkout is reused while that tag stays current.
| Status | Share | Meaning |
ok (4,148)
| 92.7% | The local repository checkout exists and matches the latest known plugin version tag. |
skipped_removed (262)
| 5.9% | The plugin has been removed from the community list, so no repository checkout is maintained. |
version_history_missing (51)
| 1.1% | The plugin entry did not have a version history available, so the latest version tag could not be selected for cloning. |
failed (16)
| 0.4% | The latest tag checkout failed during repository cloning. |
Release Acquisition Status
This table breaks down the outcomes of the latest release acquisition attempts for active plugins. We only download the main.js asset from the latest
release if there was a new release since the last successful acquisition or if we have never successfully acquired it before. This means that a status of main_js_not_updated_since_success is not necessarily a negative outcome, but rather an indication that the previously cached main.js is still considered up-to-date and useful for
analysis.
| Status | Share | Meaning |
main_js_not_updated_since_success | 57.3% | Checked, but kept the previous main.js cache. |
ok | 40.5% | Release and analyzable main.js fetched. |
version_history_missing | 1.6% | The plugin entry did not have a version history available during release acquisition, which is required to determine the latest version. |
no_release_for_version | 0.4% | No release was found that satisfied the version requirement for this plugin. |
rate_limited | 0.1% | The release acquisition attempt was blocked by GitHub rate limits. |
no_main_js_asset | 0% | Release exists, but no main.js asset was found. |
no_release | 0% | No latest release was available on GitHub. |
Repository Analysis Errors
This table summarizes the most common errors encountered during repository analysis for active plugins in the latest run. Repository analysis involves cloning
plugin repositories and extracting metadata and information from their contents.
| Error | Share | Meaning |
repository_missing (11)
| 0.3% | Less common edge-case status from repository analysis. |
manifest_parse_error (2)
| 0% | manifest.json exists but is not valid JSON for the expected schema. |
manifest_read_error (1)
| 0% | manifest.json could not be read from a cloned repository. |
