backstage/community-plugins

Community plugins for Backstage

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

backstage/community-plugins has 400+ stars and 700+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 19, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 53 minutes ago
Added to GitGenius on October 15th, 2026
Created on January 29th, 2024
Open Issues & Pull Requests: 464 (+0)
GitHub issues: Enabled
Number of forks: 713
Total Stargazers: 423 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.0 days
Mean response time: 18.3 days
90th percentile: 57.3 days
Tracked items: 563

Maintainer activity

45 people did triage or write work on this repository in the last 12 months.

At least 18% of community-plugins's 45 maintainers work at Red Hat. 27 say where they work, and 8 of those are Red Hat.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. 89% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "plugin" is answered fastest, typically in about 21 hours, while "contribfest" waits about 7 days. Almost all tracked open issues have seen activity in the last three months. 80% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 63
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 326 days
Stale 30+ days: 19
Stale 90+ days: 8

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 8
Events in 7 days: 41

Top labels

  • bug (293)
  • stale (230)
  • enhancement (199)
  • help wanted (198)
  • contribfest (65)
  • plugin (48)
  • workspace/rbac (43)
  • workspace/announcements (33)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Backstage Community Plugins is a repository hosting framework that enables community members to develop, maintain, and share plugins for the Backstage developer portal platform.

The repository addresses the challenge of managing plugin development outside the core Backstage codebase. It provides plugin maintainers with standardized tools, workflows, and release processes to efficiently publish and maintain their plugins. The architecture organizes plugins into topic-based workspaces, each with isolated releases and changesets, allowing plugins to depend on one another through standard npm dependencies regardless of whether they are core plugins, community plugins, or external packages. Workspaces are designed to be portable enough to migrate to independent repositories if needed.

Contributors should choose this repository if they want to leverage established community processes and collective knowledge rather than managing plugin development independently. It suits plugins that enhance Backstage functionality but are not essential to core platform operation. Self-hosting remains a valid alternative for those seeking full autonomy over their plugin's development and release lifecycle. Plugins critical to Backstage's fundamental functionality continue to reside in the main backstage repository to ensure central management of core components.

The project maintains active community engagement through structured contribution guidelines and a formal proposal process for new plugins. Development follows a changeset-based workflow where new changes trigger automated version and changelog updates, with merged version pull requests triggering releases across affected workspaces. The repository includes comprehensive documentation covering plugin ownership, package details, contribution procedures, and workspace setup guidance.