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 27, 2026 at 7:31 AM UTC |
| Latest plugin download snapshot | April 27, 2026 |
| Latest Obsidian release tracked | 1.12.7 on March 23, 2026 |
| Plugin records | 2,924 total (2,750 active, 174 removed)
|
| Theme records | 470 total (415 active, 55 removed)
|
Pipeline Status
| Stage | Freshness | Status |
| Community plugin dataset | April 27, 2026 | 2,924 plugins and 48,523 version snapshots processed |
| Repository cloning | April 27, 2026 at 7:30 AM UTC | 2,749 cloned, 1 failed, 174 skipped |
| Plugin releases | April 27, 2026 at 7:31 AM UTC | 2,726 successful main.js acquisitions (99%) |
| Repository analysis | April 27, 2026 at 7:31 AM UTC | 2,749 active plugins analyzed, 1 misses |
| Obsidian releases | April 27, 2026 at 7:31 AM UTC | 168 GitHub releases, 453 changelog
entries |
Pipeline Errors
- 1 repo clone failures: obsidian-audio-notes.
- 1 active plugins did not produce repo analysis data, including obsidian-audio-notes.
- 3 plugin release checks ended in an error or rate-limit state.
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 | 96.3% | Checked, but kept the previous main.js cache. |
ok | 2.7% | Release and analyzable main.js fetched. |
no_release | 0.5% | No latest release was available on GitHub. |
no_main_js_asset | 0.4% | Release exists, but no main.js asset was found. |
rate_limited | 0.1% | Less common edge-case status from the release fetch pipeline. |
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 (1)
| 0% | Less common edge-case status from repository analysis. |
