npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nospt/plugin-dev-ai-hub

v1.1.2

Published

Frontend plugin for Dev AI Hub

Readme

@nospt/plugin-dev-ai-hub

The frontend half of Dev AI Hub — a catalog-backed browser for AI assets usable by GitHub Copilot, Claude Code, Google Gemini, Cursor and other AI coding tools.

Requires Backstage 1.54 or later. The AiResource kind comes from Backstage's own alpha catalog module, and these packages depend on @backstage/catalog-model@^1.10.0 — first shipped in 1.54.0, along with the plugin and marketplace subtypes.

The Dev AI Hub browse page

What it is

Teams accumulate AI assets — a prompt that writes good commit messages, an agent that reviews code, an MCP server config for Grafana — and they end up scattered across repos, wikis and chat threads. Dev AI Hub gives them one page in Backstage, with the catalog as the source of truth.

Six kinds of resource, each with its own install path:

| Type | What it is | |---|---| | skill | Reusable instructions an AI tool loads on demand | | agent | A specialised assistant with its own system prompt | | hook | Something that runs on a tool event, e.g. lint after an edit | | mcp-config | An MCP server configuration to merge into your tool | | plugin | A bundle of the above, installed from a marketplace | | marketplace | A catalog of plugins you register with your tool once |

What a user does with it

  1. Browses — type tiles double as filters; search covers name, description and tags; further filters narrow by AI tool and tag.
  2. Opens a resource — a drawer shows the metadata plus the body, resolved on demand from wherever it lives in Git. Markdown is rendered; an mcp-config is shown as copyable JSON.
  3. Installs it — the dialog gives per-framework install paths, a copy button, a download where the body is the artifact, and one-click launchers where the tool has a URL handler.

Every resource opened or installed is counted, so the cards can show what colleagues actually use.

Install

yarn --cwd packages/app add @nospt/plugin-dev-ai-hub

This plugin uses the Backstage New Frontend System. In packages/app/src/App.tsx:

import { devAiHubPlugin } from '@nospt/plugin-dev-ai-hub';

export const app = createApp({
  features: [
    // ...existing features
    devAiHubPlugin,
  ],
});

The sidebar item and the /dev-ai-hub route register themselves.

You also need

  • @nospt/plugin-dev-ai-hub-backend — the page has nothing to show without it.
  • @backstage/plugin-catalog-backend-module-ai-model — provides the AiResource kind.
  • AiResource allow-listed in your catalog.rules, and at least one entity registered.

All three are covered in the repository README, which is the single place kept current.

Configuration

devAiHub:
  ui:
    # Optional. Width of the resource detail drawer, in pixels. The drawer is
    # an overlay, so this never reflows the page; it is capped at the viewport
    # width and floored at a sane minimum. Defaults to 615 when unset.
    detailPanelWidth: 615

The framework allow-list (devAiHub.frameworks.allowed) is enforced by the backend plugin — see its README.

Troubleshooting

| Symptom | Usually means | |---|---| | The page loads but says "Register AiResource entities…" | The catalog has no AiResource entities — or they were rejected because the kind is not in catalog.rules | | "Could not load resources" | The backend plugin is not registered, or the request is unauthenticated | | Components render unstyled | @backstage/ui/css/styles.css is not imported in packages/app/src/index.tsx — apps scaffolded by a current create-app already do this | | A resource is listed but has no install actions | It publishes no backstage.io/source-location, so it is browsable but not installable |

License

Apache-2.0