The Future of Obsidian Plugins: Community Hub, Automated Reviews, and the Road Ahead (2026 Guide)
Big changes are coming to the Obsidian plugin ecosystem. On May 12, 2026, Obsidian published a detailed roadmap for the future of their plugin system — introducing a brand new Community Hub, an automated review system, a developer dashboard, and ambitious plans for plugin safety, discovery, and API stability. With over 4,000 plugins and themes and more than 120 million total downloads, this is the most significant infrastructure upgrade Obsidian's ecosystem has ever seen.
This guide breaks down everything announced, what it means for plugin developers and users, and how the Obsidian plugin landscape will evolve.
Obsidian's plugin ecosystem is arguably its single biggest competitive advantage over other note-taking and knowledge management tools. From graph visualizations and Kanban boards to AI-powered writing assistants and databases — the community has built an astonishing range of extensions that transform Obsidian from a simple Markdown editor into a flexible knowledge platform. The new initiatives aim to make this ecosystem healthier, safer, and more sustainable.
The Obsidian Plugin Ecosystem in Numbers
Before diving into what's changing, let's appreciate the scale of the Obsidian plugin community:
- 4,000+ plugins and themes created since the Obsidian API launched in 2020
- 120 million+ total plugin downloads
- 2,300+ queued submissions were processed in the first few days of the new automated review system
- Dozens of categories ranging from Integrations and Bases to Charts, AI, and project management
These numbers reveal a thriving ecosystem that has outgrown its original manual-review infrastructure. The old process — where every new plugin was manually reviewed by Obsidian's small team — simply couldn't scale to thousands of submissions and updates. Obsidian acknowledged this openly in their announcement: "As coding agents accelerate the creation of plugins, the review queue was only getting longer."
Key insight: Obsidian is explicitly acknowledging that AI coding agents (like Claude Code, Cursor, and GitHub Copilot) are accelerating plugin creation. The automated review system is designed to handle this new reality where more people can build plugins than ever before.
The New Community Hub: Plugin Discovery 2.0
The centerpiece of Obsidian's announcement is the new Obsidian Community site — a complete redesign of how users discover and evaluate plugins and themes.
What's New in Discovery
- Categorized browsing — Browse plugins across dozens of categories: Integrations, Bases, Charts, and many more. This replaces the old flat list.
- Advanced filtering and sorting — Sort by name, downloads, popularity, release date, or last updated. Filter by official status, paid status, or category.
- Individual project pages — Every plugin and theme now has its own detail page with screenshots, descriptions, and a safety scorecard.
- Labels — New labels for paid plugins, optional payments, and official integrations.
- Author profiles — Developers can customize their profiles with sponsorship links, websites, and social media.
The old in-app plugin browser was functional but limited. The new Community site brings Obsidian's plugin discovery on par with marketplaces like VS Code Extensions or the Chrome Web Store — with richer metadata, better search, and transparency features.
Developer Dashboard: Claim, Manage, and Track
The new developer dashboard is a significant upgrade for plugin creators. Instead of managing submissions through GitHub repositories and waiting for manual approval, developers now have a central console for their Obsidian plugins and themes.
Key Features
- Automatic migration — All existing plugins, themes, and queued submissions submitted via GitHub have been automatically migrated to the new site.
- GitHub account linking — Sign in with your Obsidian account, connect GitHub, and claim your existing projects.
- Submission management — New streamlined submission flow with near-instant results (typically within minutes).
- Status tracking — See exactly where your plugin stands in the review pipeline.
- Profile customization — Edit titles, descriptions, screenshots, and sponsorship options.
One interesting detail: developers can still release new versions via GitHub without using the developer dashboard. New releases are automatically reviewed. However, if an update fails to pass review, developers must use the dashboard to see detailed error information.
Pro tip: Run automated reviews locally before submitting. Use Obsidian's eslint plugin to check your plugin against official guidelines, or use the developer dashboard to run a preview scan on any branch, tag, or commit.
Automated Reviews: Security at Scale
This is arguably the most impactful change. Obsidian has replaced the old manual-only review process with a hybrid system that combines automated scanning for every version with targeted manual reviews for high-impact plugins.
How the New Review System Works
- Every version is scanned — Not just initial submissions. Each update triggers automated checks for code quality, best practices, known vulnerabilities, and malware.
- Results in minutes — Instead of waiting days or weeks for manual approval, submissions are typically reviewed within minutes.
- Scalable improvements — Obsidian can continuously improve their automated tests, making the entire ecosystem more secure over time.
- Manual reviews continue — The team shifts focus to plugins that need deeper inspection: popular plugins, featured plugins, and community-flagged issues.
The numbers speak for themselves: in the first few days, the system processed 2,300+ queued submissions — a backlog that would have taken months under the old manual process.
Enforcement
All new plugins and themes must pass automated review before appearing in search results. If a version fails review, the plugin is removed from search within 24 hours. Older plugins that predate the new system have been granted a temporary exception, but eventually all plugins must meet the new standards.
Plugin Safety: Scorecards, Disclosures, and Verified Authors
Security and transparency are major themes in Obsidian's roadmap. The new system introduces several layers of safety:
Safety Scorecards
Every plugin now displays a safety scorecard showing the status of automated checks. These scorecards will evolve to include:
- Automated scan results (code quality, vulnerabilities, malware checks)
- Disclosures — what capabilities the plugin accesses (network, file system, clipboard)
- Privacy labels
- Artifact attestation
- Manual review results
- Adoption of app capabilities
Disclosures (Coming Soon)
Plugins will be required to declare what they access: network, file system, clipboard, and other capabilities. Users will see these disclosures before installing plugins — similar to mobile app permissions.
Verified Authors (Coming Soon)
Trusted developers who pass additional verification steps will receive a verified author badge. This helps users distinguish well-established developers from new or unknown publishers.
Community Reporting
Users can always flag security issues directly to the Obsidian team, adding a human layer to the automated system.
API Stability: What Developers Can Count On
While Obsidian's blog post focused on infrastructure and safety, the topic of API stability is implicit in their broader strategy. With the introduction of automated reviews that check against developer policies and best practices, Obsidian is signaling a more mature, stable API contract.
For developers looking to build Obsidian plugins, the current API — accessed via the Obsidian developer documentation — supports:
- Vault access — Read, write, and manipulate vault files and folders
- View customization — Custom views, panes, and editors
- Event hooks — React to file changes, vault events, and user actions
- UI components — Reusable Obsidian-native UI elements
- Settings API — Plugin configuration interfaces
- Command palette — Register custom commands
- Ribbon icons — Add icons to the sidebar
With the automated review system, developers now have clear, enforceable guidelines for what constitutes a well-built plugin. The Developer Policies and the eslint plugin provide concrete guardrails that make the API ecosystem more predictable.
Tools for Teams
Obsidian is also investing in enterprise and team features:
- Safety controls — Teams can already deploy safety controls for their users.
- Plugin allowlists — Coming soon: tools for team admins to manage which community plugins are allowed.
- Private plugins — Teams will be able to distribute private plugins to team members.
- Official badge — Organizations publishing official Obsidian plugins can apply for the Official badge in the Community directory.
These features address a growing use case: organizations adopting Obsidian as their knowledge management tool need the same kind of access controls and compliance features they expect from enterprise software.
What This Means for Plugin Developers
If you're a developer — or aspiring to become one — here's what the new ecosystem means for you:
Opportunities
- Faster time to market — Submit a plugin and get results in minutes instead of weeks.
- Clear quality standards — The eslint plugin and automated reviews give you objective targets to aim for.
- Better discoverability — The new Community site with categories, sorting, and detail pages makes it easier for users to find your plugin.
- Monetization options — Paid and optional payments labels are now officially supported in the directory.
- AI-assisted development — With tools like Obsidian CLI, creating plugins is becoming easier than ever.
How to Get Started
- Create an Obsidian account
- Read the Obsidian Developer Documentation
- Use obsidian-sample-plugin as a starting template
- Install the eslint plugin for local validation
- Build, test locally, then submit via the developer dashboard
Important Considerations
Some things to keep in mind:
- Closed-source plugins — New closed-source plugins are not being accepted. Existing ones continue for now.
- Active maintenance required — Plugins that are no longer maintained may be removed.
- GitHub required — The developer dashboard currently only supports GitHub. Other platforms may come later.
- Sample code — Use the official sample plugin to get started quickly.
- Join the community — The #plugin-dev channel on the Obsidian Discord is the best place for developer support.
What This Means for Plugin Users
For the average Obsidian user — hundreds of thousands of people who rely on plugins daily — these changes are overwhelmingly positive:
- Better discovery — The new Community site makes it easier to find the right plugin for your needs with categories, filtering, and detailed pages.
- Increased safety — Every plugin is scanned for malware and vulnerabilities. Scorecards make security transparent.
- Faster access — New plugins and updates are available much faster now that reviews are automated.
- More visibility — Payment labels (free, optional payments, paid) help you understand costs before installing.
- Team controls — If your organization uses Obsidian, admins will have better tools to manage plugin access.
Important note for users: Safety scorecards are new and may contain errors (false positives and false negatives). If you notice something inaccurate, contact the Obsidian team via the #plugin-dev channel on Discord.
Frequently Asked Questions
Can I still update my plugin via GitHub without using the dashboard?
Yes. New releases via GitHub are automatically reviewed. However, if an update fails review, you'll need the dashboard to see the details.
What happens to old/unmaintained plugins?
They remain available for now but will eventually be required to meet the new standards. No deadline has been set, and Obsidian is working with the community on the transition.
Can I run the automated review locally?
Yes. Use the eslint plugin to check against guidelines, or use the developer dashboard to run a preview scan on any branch/tag/commit.
Can multiple developers manage one plugin?
Currently only the GitHub repo owner can edit a plugin. Support for multiple collaborators is planned.
What does "Paid" vs "Optional Payments" mean?
"Free" means no payment required. "Optional Payments" means users may pay for extra features or the plugin connects to paid services. "Paid" means users must pay for primary features.
Does the developer dashboard require an Obsidian account?
Yes, and you also need to connect your GitHub account to claim existing plugins or submit new ones.
The future of Obsidian plugins is brighter than ever. With the new Community Hub, automated reviews, developer dashboard, and safety features, Obsidian is building the infrastructure for a plugin ecosystem that can scale to 10x its current size. For developers, the path to building and distributing plugins has never been clearer or faster. For users, the plugin experience is about to become safer, more transparent, and easier to navigate.
Explore the new Obsidian Community site and see what the future looks like.