This page provides insights into the most recent data update for Obsidian Stats. It covers the freshness of the data, the amount of datapoint processed, and highlights errors encountered during the update process.
| Metric | Value |
| Latest pipeline activity | April 14, 2026 at 10:36 AM UTC |
| Latest plugin download snapshot | April 14, 2026 |
| Latest Obsidian release tracked | 1.12.7 on March 23, 2026 |
| Plugin records | 2,924 total (2,754 active, 170 removed)
|
| Theme records | 470 total (416 active, 54 removed)
|
Pipeline Status
| Stage | Freshness | Status |
| Community plugin dataset | April 14, 2026 | 2,924 plugins and 48,287 version snapshots processed |
| Repository cloning | April 14, 2026 at 10:36 AM UTC | 2,752 cloned, 2 failed, 170 skipped |
| Plugin releases | April 13, 2026 at 10:51 AM UTC | 2,727 successful main.js acquisitions (99%) |
| Repository analysis | April 13, 2026 at 10:51 AM UTC | 2,752 active plugins analyzed, 2 misses |
| Obsidian releases | April 13, 2026 at 10:51 AM UTC | 168 GitHub releases, 453 changelog
entries |
Pipeline Errors
- 2 repo clone failures: obsidian-audio-notes, fleeting-notes-obsidian.
- 2 active plugins did not produce repo analysis data, including obsidian-audio-notes, fleeting-notes-obsidian.
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 |
ok | 95.5% | Release and analyzable main.js fetched. |
main_js_not_updated_since_success | 3.5% | Checked, but kept the previous main.js cache. |
no_release | 0.6% | No latest release was available on GitHub. |
no_main_js_asset | 0.4% | Release exists, but no main.js asset was found. |
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 |
package_json_read_error (10)
| 0.4% | package.json could not be read even though it was detected in the repository. |
manifest_parse_error (3)
| 0.1% | manifest.json exists but is not valid JSON for the expected schema. |
repository_missing (2)
| 0.1% | Less common edge-case status from repository analysis. |
