obsidianmd/obsidian-releases

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

Sans licence Dernier commit il y a 5 heures obsidian.md

Mis à jour il y a 16 min

Ouvrir sur GitHub

24 dernières heures: +26; étoiles
7 derniers jours: +221; étoiles
30 derniers jours: +795; étoiles
Étoiles au total: 22 420
Forks: 7 875

Historique des étoiles

Total d’étoiles à la fin de chaque semaine, d’après les comptes quotidiens de GitHub.

+221 étoiles cette semaine, contre ~173 une semaine habituelle

Rang dans ses thèmes

Parmi les dépôts qui ont gagné au moins 20 étoiles sur la période

Rang de obsidianmd/obsidian-releases dans chaque thème pour aujourd’hui, cette semaine et ce mois-ci
Thème	Aujourd’hui	Cette semaine	Ce mois-ci
Local-first thème	#38sur 40	#100sur 142	#134sur 238

Signaux de santé

Signaux mitigésVérifié le 18 oct. 2026

Activité des commits: Des commits 13 semaines sur les 13 dernières 1 440 commits sur la branche principale en 90 jours
Mainteneurs: Aucun commit humain en 90 jours
Réactivité sur les issues: Trop peu d’issues pour juger 0 issue ouverte par d’autres en 90 jours
Pull requests: Aucune ouverte en 90 jours
Versions: Dernière version : il y a 2 semaines 12 versions ces 12 derniers mois
Hygiène du projet: CI ; pas de licence ou politique de sécurité
OpenSSF Scorecard: 3,7 / 10 (nouvel onglet) Analysé le 12 oct. 2026

Ces signaux sont calculés automatiquement à partir des données publiques de GitHub. Ce n’est ni une recommandation ni un audit de sécurité. Comment la santé est calculée

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.