mvanhorn/printing-press-library

Add npm registry intelligence CLI

Open

#1,182 opened on 2026年6月15日

GitHub で見る
 (1 comment) (0 reactions) (1 assignee)Go (371 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (1,443 stars)
PR merge metrics
 (PR metrics pending)

説明

Goal

Add a Printing Press CLI for npm package intelligence: metadata, releases, maintainers, downloads, dependency risk, and package comparisons.

Free source

  • npm registry API.
  • npm downloads API.

Agent jobs

  • Decide whether a package is healthy enough to use.
  • Compare packages by freshness, downloads, maintainers, license, dependency surface, and release cadence.
  • Spot stale or risky transitive dependencies.
  • Build a short package brief for engineering decisions.

Proposed command shape

  • npm-intel-pp-cli package react --agent
  • npm-intel-pp-cli compare axios got undici --agent
  • npm-intel-pp-cli downloads zod --period last-month --agent
  • npm-intel-pp-cli releases vite --since 90d --agent
  • npm-intel-pp-cli maintainers left-pad --agent
  • npm-intel-pp-cli risk <package> --agent

Non-goals

No publishing, token use, package deletion, or account mutation.\n\n## Implementation path\n\nThis is a new CLI candidate, so do not hand-build it directly in this published library repo. Run it through the canonical Printing Press generation flow in cli-printing-press, keep manuscripts/proofs, then publish into this repo with the publish flow.\n\n## Acceptance criteria\n\n- Research notes explain the source/API/feed contract, rate limits, auth needs, and freshness behavior.\n- CLI exposes a small agent-native command set, not a raw endpoint dump.\n- --json / --agent output is stable and compact.\n- If the source benefits from history, add local SQLite sync plus since/diff commands.\n- Skill includes high-signal recipes and clear non-goals.\n- Dogfood proves at least three realistic agent workflows.

コントリビューターガイド