cursor/community-plugins

Plugins from the Cursor community

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 17th, 2026
Created on August 24th, 2024
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 671
Total Stargazers: 3,991 (+0)
Total Subscribers: 24 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.8 days
Mean response time: 43.1 days
90th percentile: 159.1 days
Tracked items: 32

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 35 days
Stale 30+ days: 6
Stale 90+ days: 0

Recent activity

Opened in 7 days: 3
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

Detailed Description

Cursor Community Plugins is a web directory that aggregates plugins from the Cursor community.

The project solves the problem of discovering and sharing Cursor plugins by providing a centralized registry. It works by allowing community members to submit plugins through a web interface that auto-detects plugin components following the Open Plugins standard, including rules, MCP servers, skills, agents, hooks, and LSP servers. Plugin submissions are automatically scanned for security using a Cursor SDK agent that analyzes the code and assigns a verdict of safe, suspicious, or malicious. All plugin data is stored in a Supabase database rather than in the repository itself.

The tool suits anyone building or distributing Cursor plugins who wants visibility in a community directory. It is designed for plugin authors who can submit their work through the web interface without needing to open pull requests. The submission process requires only a GitHub repository URL, and the system handles component detection automatically based on the Open Plugins specification.

The project typically takes one to two weeks to respond to issues or pull requests.