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

@b-apm/integration-kiro

v0.1.1

Published

Kiro IDE/CLI runtime integration for bapm

Readme

@b-apm/integration-kiro

UNSTABLE: Early public release. APIs and on-disk layouts may change without a major bump. Not production-ready.

Kiro IDE/CLI runtime host for bapm (project-scope .kiro/ primitives + translate MCP).

Opt-in load

npm i -D @b-apm/integration-kiro
targets:
  kiro: "@b-apm/integration-kiro"
active:
  - kiro
bapm init -y --target kiro
bapm install --target kiro
bapm compile --target kiro

Detection vs forced target

| Mode | When active | Creates roots? | | ---------------------------- | --------------------------------- | --------------------------------------------------- | | Auto-detect | Project .kiro/ directory exists | Only when materialize / configure runs after detect | | Forced (--target kiro) | Explicit forced target id | MAY mkdir .kiro/ as needed |

Auto-detect without .kiro/ MUST NOT create the directory solely for detection.

Deploy roots

  • .kiro — steering, agents, skills, hooks, MCP settings, ownership sidecar
  • . — thin AGENTS.md compile output

Materialize routing

| Primitive type | Destination | | ---------------- | --------------------------------------------------------------------------------------------------- | | instruction | .kiro/steering/<name>.md (applyToinclusion: fileMatch + fileMatchPattern; else always) | | agent | .kiro/agents/<name>.md (FM: description / model / tools only; tools fail-closed) | | skill | .kiro/skills/<name>/ (never .agents/skills/) | | hook | per-file .kiro/hooks/<pkg>-<stem>-<event>-<n>.json (v1 + scripts) + .kiro/bapm-hooks.json | | command / prompt | skipped (APM matrix N) |

MCP is not written by materialize — only via configureMcp.

MCP (translate)

  • Config: .kiro/settings/mcp.json (mcpServers), opt-in when .kiro/ exists
  • mcpEnvMode: "translate" — APM ${VAR} / ${env:VAR} / <VAR> stay as runtime ${VAR}
  • Unrelated servers and top-level keys are preserved

Compile

Thin emitter → AGENTS.md. Instruction primitives already deployed as steering are omitted from the compile body.

Exports

  • createKiroIntegration / createIntegration — runtime factory (id: "kiro")
  • KIRO_AGENT_ALLOWED_TOOLS — approved capability tags
  • transformKiroSteeringMarkdown — instruction → steering helper