Community plugins for Backstage
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 70%
Response Time: -
First Timer Success: 57%
backstage/community-plugins has a recorded first-timer success rate of 57.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in backstage/community-plugins respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 67.6 places backstage/community-plugins in the A tier.
The external contributor pull request merge rate for backstage/community-plugins is 70.2%, based on public PR activity from non-core contributors.
backstage/community-plugins currently has 18 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Community plugins for Backstage
Highly welcoming maintainers in backstage/community-plugins. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/backstage/community-plugins?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (88% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
Workspace tech-insights 🔖 Feature description tech insights plugins should have MCP actions so that user can query tech insights from their AI CLIs and interact with tech insights and service maturity. 🎤 Context Backstage catalog and scaffolder already supports this, following the same pattern, we can have it in tech insights as well so users can query tech insights from claude, codex, opencode. ✌️ Possible Implementation I have already implemented it as backstage plugin but I am happy to contribute it within tech insights. 👀 Have you spent some time to check if this feature request has been raised before? I checked and didn't find similar issue 🏢 Have you read the Code of Conduct? I have read the Code of Conduct Are you willing to submit PR? Yes I am willing to submit a PR!
Workspace graphiql 📜 Description Version:0.19.0 GraphiQLEndpointBlueprint's attachTo targets an extension id that the plugin never actually registers, so no endpoint configured via graphiql-endpoint:graphiql/* — including the plugin's own built-in gitlab example — ever reaches the GraphiQL page. The page always renders "No endpoints available" regardless of app-config. 👍 Expected behavior An endpoint configured via a graphiql-endpoint:graphiql/* extension (either the built-in gitlab example enabled through app-config.yaml, or a custom one declared with GraphiQLEndpointBlueprint.make({...})) should appear as a tab on the /graphiql page and be usable. 👎 Actual Behavior with Screenshots The /graphiql page always shows "No endpoints available", no matter what is configured. No error or warning is logged anywhere (browser console or backend logs) indicating the endpoint failed to attach — it fails completely silently. 👟 Reproduction steps Install @backstage-community/plugi
Workspace grafana 📜 Description My backstage version is: 1.54.6 I am using New Front End System and configured Grafana Plugin. Dashboard and alerts appears in Entity page, except that Alerts Dont show "State" Column. 👍 Expected behavior Alerts Should Show both name and state column as per: https://github.com/backstage/community-plugins/blob/main/workspaces/grafana/plugins/grafana/docs/alerts_card.png 👎 Actual Behavior with Screenshots 👟 Reproduction steps 1.Using New Front End System in Backstage 2. Configure Grafana Plugin: https://github.com/backstage/community-plugins/blob/main/workspaces/grafana/plugins/grafana/docs/setup.md 3. Go to Entity page 4. Look at Alerts Section 📃 Provide the context for the Bug. No response 👀 Have you spent some time to check if this bug has been raised before? I checked and didn't find similar issue 🏢 Have you read the Code of Conduct? I have read the Code of Conduct Are you willing to submit PR? No, but I'm happy to collabo
Workspace tech-radar 📜 Description If a tech radar has not data for all four quadrants (e.g. only three quadrants) then a error appears. In older versions (e.g. 0.7.11) it works without errors. 👍 Expected behavior The tech radar should be displayed, only the quadrants without data should be empty(also without legend). This was the behaviour in older versions, like 0.7.11. 👎 Actual Behavior with Screenshots Instead of the tech radar the following error will be displayed fullsized in the browser: 👟 Reproduction steps create a tech radar with only data for e.g. 3 quadrants 📃 Provide the context for the Bug. According to quick look in the source code of the plugin, the reason ist probably the access of array elements of adjustedQuadrants without checking if this array element exists at all (e.g. inRadar.tsx line 61 and 62, perhaps there are other places as well). btw: The introductory comment of adjustQuadrants in utils.ts is incorrect, and maybe could also be fixed: xSt
Workspace jenkins 🔖 Feature description Allow an entity's jenkins.io/job-full-name annotation to reference jobs from more than one named Jenkins instance, so a single component can show/trigger CI status across instances instead of being locked to just one. 🎤 Context We run a few named Jenkins instances behind one Backstage (jenkins.instances[]) — say prod and dev to keep it generic. A project's jobs are genuinely spread across instances (some run on prod, others on dev), and we'd like one entity to reflect all of them. Right now, listing jobs from more than one instance — jenkins.io/job-full-name: prod:jobX,dev:jobY — throws straight out of DefaultJenkinsInfoProvider.getInstance(): More than one Jenkins instance found: (prod,dev) on entity with name: ... Please use the same instance for all jobs. That's not just an overzealous validation: getInstance() returns a single JenkinsInfo with one baseUrl and one set of auth headers for the whole fullJobNames list, so there's nowh
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to backstage/community-plugins, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of backstage/community-plugins acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.2% were successfully merged into the primary branch.
backstage/community-plugins has a recorded first-timer success rate of 57.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 67.6 places backstage/community-plugins in the Welcoming tier.
The external pull request merge rate is 70.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, backstage/community-plugins currently has 18 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for backstage/community-plugins are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.