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

@gpcola/devplan-tracker

v1.0.2

Published

Dependency-free DEVPLAN tracker CLI and repository pack for software projects.

Readme

DEVPLAN Tracker

A dependency-free DEVPLAN tracker for any software repository. It keeps a human-readable devplan/DEVPLAN.md and machine-readable devplan/DEVPLAN-STATE.json aligned so humans, CI, and AI agents can see what is planned, blocked, done, and release-critical.

Requirements

  • Node.js 18 or newer; Node.js 22 LTS is recommended.
  • No runtime dependencies and no external services.

Quick start in this repo

node scripts/devplan.mjs validate
node scripts/devplan.mjs status
node scripts/devplan.mjs next
node scripts/devplan.mjs report --output /tmp/devplan-report.md
node scripts/devplan.mjs readiness

The default layout is:

devplan/
  DEVPLAN.md
  DEVPLAN-STATE.json
  devplan.config.json
  docs/
  reports/
  schemas/

Install into another repository

From a checkout of this package:

node install.mjs --target /path/to/repo

From GitHub once this repository is pushed:

npx github:gpcola/devplan-tracker init

After npm publication:

npx @1lg/devplan-tracker init

The installer skips existing files unless --force is provided. If the target has a package.json, scripts from package-scripts.json are merged without removing existing scripts. If no package.json exists, the installer prints manual script instructions.

Commands

  • init installs the tracker into devplan/ by default.
  • migrate moves legacy root DEVPLAN.md and DEVPLAN-STATE.json files into devplan/.
  • status prints project, branch, status counts, and milestones.
  • validate checks JSON parsing, schema version, metadata, statuses, unique IDs, milestone references, required item fields, and devplan/DEVPLAN.md references.
  • next lists the highest-priority open work.
  • report emits a Markdown report.
  • readiness exits successfully only when no release-critical items are blocked or open.
  • list filters tracked items.
  • add-milestone, add-item, update, remove-item, link-item, and protect mutate state safely.

Installer options

  • --target <path> installs into another repository.
  • --force overwrites existing tracker files and package scripts.
  • --root-files uses the legacy root-level layout.
  • --local-only adds installed tracker files to .gitignore for local-only use.

Agent rule

Any PR that changes tracked work must update devplan/DEVPLAN-STATE.json in the same PR. Completed work needs evidence and success conditions must remain testable.

More documentation

See devplan/docs/USAGE.md, devplan/docs/GOVERNANCE.md, devplan/docs/AGENT-INSTRUCTIONS.md, devplan/docs/CI.md, and devplan/docs/MIGRATION.md.