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 | July 13, 2026 at 6:24 PM UTC |
| Latest plugin download snapshot | July 13, 2026 |
| Latest Obsidian release tracked | 1.12.7 on March 23, 2026 |
| Plugin records | 6,066 total (5,649 active, 417 removed) |
| Theme records | 693 total (626 active, 67 removed) |
Pipeline Status
| Stage | Freshness | Status |
|---|
| Community plugin dataset | July 13, 2026 | 6,066 plugins and 52,325 version snapshots processed |
| Repository cloning | July 13, 2026 at 6:23 PM UTC | 5,284 current tag checkouts, 2 failed, 443 removed skipped |
| Plugin releases | July 13, 2026 at 6:23 PM UTC | 5,508 successful main.js acquisitions (93.3%) |
| Repository analysis | July 13, 2026 at 6:23 PM UTC | 5,610 active plugins analyzed, 39 misses |
| Obsidian releases | July 13, 2026 at 6:24 PM UTC | 168 GitHub releases, 457 changelog entries |
Pipeline Errors
- 2 repo clone failures: cyberware, hide-tags.
- 39 active plugins did not produce repo analysis data, including agent-mcp, ai-book-manager, auto-beautiful-mermaid, canvas-branch-chat, copy-file-to-clipboard.
- 379 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 (5,284) | 86.7% | The local repository checkout exists and matches the stats-helper manifest version tag. |
skipped_removed (443) | 7.3% | The plugin has been removed from the community list, so no repository checkout is maintained. |
manifest_missing (308) | 5.1% | The stats-helper plugin entry did not have a manifest available for cloning. |
release_for_manifest_version_missing (24) | 0.4% | The stats-helper releases did not contain a tag matching the manifest version. |
manifest_version_invalid (19) | 0.3% | The stats-helper manifest version was not valid for cloning. |
helper_plugin_missing (16) | 0.3% | The stats-helper data did not contain a matching plugin entry for cloning. |
failed (2) | 0% | The latest tag checkout failed during repository cloning. |
version_history_missing (2) | 0% | Legacy status: the plugin entry did not have version history available. |
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 | 64.8% | Checked, but kept the previous main.js cache. |
ok | 28.4% | Release and analyzable main.js fetched. |
manifest_missing | 5.2% | Stats-helper manifest was missing. |
release_for_manifest_version_missing | 0.5% | No stats-helper release matched the manifest version. |
helper_plugin_missing | 0.4% | Stats-helper plugin data was missing. |
manifest_version_invalid | 0.3% | Stats-helper manifest version was invalid. |
version_history_missing | 0.2% | Legacy status: the plugin entry did not have version history available. |
no_main_js_asset | 0.1% | Release exists, but no main.js asset was found. |
no_release | 0% | Legacy status: no 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 |
|---|
main_js_analysis_too_large (48) | 0.8% | The cached release main.js was too large to parse safely, so main.js-specific analysis was skipped. |
repository_missing (39) | 0.7% | The expected local plugin repository checkout was missing during analysis. |
manifest_read_error (6) | 0.1% | manifest.json could not be read from a cloned repository. |
manifest_parse_error (2) | 0% | manifest.json exists but is not valid JSON for the expected schema. |
