obsidianmd/obsidian-sample-plugin

Template for Obsidian community plugins with build configuration and development best practices.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 52 minutes ago
Type:Template / ExampleCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on September 15th, 2026
Created on October 25th, 2020
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 1,781
Total Stargazers: 4,534 (+0)
Total Subscribers: 44 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 hours
Mean response time: 63.7 days
90th percentile: 137.5 days
Tracked items: 27

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 418 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Obsidian Sample Plugin is a template for building community plugins for Obsidian that provides build configuration and development best practices.

The template addresses the need for a standardized starting point when developing Obsidian plugins. It demonstrates core plugin API functionality including ribbon icons, modals, settings tabs, global event listeners, and interval-based operations. The project uses TypeScript to provide type checking and documentation, with the plugin API available as TypeScript definitions containing TSDoc comments. Developers clone the template, install dependencies with npm, and run a development server that automatically compiles changes from the source TypeScript file to the output JavaScript file.

The template suits developers new to Obsidian plugin development who want to understand basic API patterns before building their own plugins. It works well for anyone creating a plugin for the Obsidian ecosystem, whether building a simple utility or a more complex feature. The README explicitly recommends checking the existing plugin directory before starting development to avoid duplicating effort.

The project maintains active engagement with plugin developers through documentation and tooling. The template includes npm scripts for development compilation in watch mode and version management. Release procedures are documented with guidance on updating manifest and version files, creating GitHub releases, and submitting plugins to the community plugin list. The repository provides clear instructions for manual plugin installation and references the plugin guidelines that developers must follow before publishing to the community.