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-cursor

v0.1.0

Published

Cursor integration for bapm

Downloads

146

Readme

@b-apm/integration-cursor

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

Minimal Cursor host for bapm (M5 polish + M9 MCP configure).

Detection vs forced target

| Mode | When active | Creates roots? | | ------------------------------ | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- | | Auto-detect | .cursor/ directory or legacy .cursorrules file at project root | Only when materialize / configureMcp runs after a positive detect | | Forced (--target cursor) | Explicit CLI/core forced target id, even if detect is false | MAY mkdir registered roots (.cursor/, .agents/skills, .cursor/rules, .cursor/agents) as needed |

Auto-detect without force MUST NOT create .cursor/ solely for MCP opt-in. Forced activation is owned by Install / CLI; this package’s detect stays an honest presence predicate.

Deploy roots (tg-002 / tg-003)

Registered roots:

  • .agents/skills — skills → <name>/SKILL.md
  • .cursor — companion root (detection + rules/agents + MCP config)

Materialize routing

| Primitive type | Destination | | -------------- | -------------------------------- | | skill | .agents/skills/<name>/SKILL.md | | instruction | .cursor/rules/<name>.mdc | | agent | .cursor/agents/<name>.md |

Thin copy/write from source content (minimal frontmatter only when content is missing). Writes are idempotent overwrites and never escape registered roots.

Skills / rules / agents materialize does not write .cursor/mcp.json. MCP config is written only via the separate configureMcp path when install requests it.

materialize returns a MaterializeReport (deployedFiles: { path }[]) via @b-apm/integration-api for lock inventory.

MCP configure (configureMcp)

When install invokes configureMcp with eligible servers:

  • Writes / updates .cursor/mcp.json under the registered .cursor/ root only
  • Shape: { "mcpServers": { "<name>": { "command"|"url"|… } } } (stdio / http)
  • Idempotent overwrite of bapm-owned server keys (keyed by server name); unknown user keys are preserved when present
  • Returns a ConfigureMcpReport (configPath, servers, deployedFiles) for lock mcp_* inventory

Dependencies

Depends only on @b-apm/integration-api among bapm packages — not @b-apm/core. Shared materialize helpers (sanitizeName, assertUnderDeployRoots, readPrimitiveContent, …) come from @b-apm/integration-api; this package keeps Cursor detect and path routing only. Register via createIntegrationRegistry().register(createCursorIntegration()) in CLI or tests.

Third-party authors publishing a custom host for object-map targets should prefer a named createIntegration factory (see @b-apm/integration-api README — loadable export contract). This package’s createCursorIntegration remains the Cursor-specific factory accepted by the CLI loader.