obsidianmd/obsidian-releases

Community plugins list, theme list, and releases of Obsidian.

No license Last commit 5 hours ago obsidian.md

Updated 14 min ago

Open on GitHub

Last 24 hours: +26; stars
Last 7 days: +221; stars
Last 30 days: +795; stars
Total stars: 22,420
Forks: 7,875

Star history

Total stars at the end of each week, from GitHub’s daily star counts.

+221 stars this week, against ~173 in a usual week

Rank in its topics

Out of repos that gained at least 20 stars in the period

Rank of obsidianmd/obsidian-releases in each topic for today, this week and this month
Topic	Today	This week	This month
Local-first topic	#38of 40	#100of 142	#134of 238

Health signals

Mixed signalsChecked Oct 18, 2026

Commit activity: Commits in 13 of the last 13 weeks 1,440 commits on the default branch in 90 days
Maintainers: No commits by people in 90 days
Issue responsiveness: Too few issues to tell 0 issues opened by others in 90 days
Pull requests: None opened in 90 days
Releases: Last release: 2 weeks ago 12 releases in the last 12 months
Project hygiene: CI; no license or security policy
OpenSSF Scorecard: 3.7 / 10 (opens in new tab) Scanned Oct 12, 2026

Signals are computed automatically from public GitHub data. They are not an endorsement or a security audit. How health is computed

README

README.md

About this repo

This repo is used for hosting public releases of Obsidian, as well as our community plugins & themes directories.

Obsidian is not open source software and this repo DOES NOT contain the source code of Obsidian. However, if you wish to contribute to Obsidian, you can easily do so with our extensive plugin system. A plugin guide can be found here: https://docs.obsidian.md

This repo does not accept issues, if you have questions or issues with plugins, please go to their own repo to file them. If you have questions or issues about core Obsidian itself, please post them to our community: https://obsidian.md/community

Submit your plugin or theme

You can find a detailed explanation for submitting your plugin here and your theme here.

Policies

All submissions must conform with our developer policies

How community plugins are pulled

Obsidian will read the list of plugins in community-plugins.json.
The name, author and description fields are used for searching.
When the user opens the detail page of your plugin, Obsidian will pull the manifest.json and README.md from your GitHub repo).
The manifest.json in your repo will only be used to figure out the latest version. Actual files are fetched from your GitHub releases.
If your manifest.json requires a version of Obsidian that's higher than the running app, your versions.json will be consulted to find the latest version of your plugin that is compatible.
When the user chooses to install your plugin, Obsidian will look for your GitHub releases tagged identically to the version inside manifest.json.
Obsidian will download manifest.json, main.js, and styles.css (if available), and store them in the proper location inside the vault.

Announcing the First Public Release of your Plugin/Theme

Once admitted to the plugin/theme community, you can announce the public availability of your plugin/theme:
- in the forums as a showcase, and
- on the Discord Server in the channel #updates. (You need the developer role to be able to post in that channel; you can get that role here.)
You can also announce the first working version of your plugin as a public beta before "officially" submitting it to the plugin/theme browser. That way, you can acquire some beta testers for feedback. It's recommended to use the BRAT Plugin to make the installation as easy as possible for interested beta testers.