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

@reactiff/dcs

v0.2.0

Published

A generic, evidence-backed Development Control System for Codex projects.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

nycdude777nycdude777

Keywords

Readme

Development Control System package

Standalone DCS package, version 0.2.0. It contains generic ledger and execution-control machinery only; project-specific product behavior belongs in the planning payload.

The package name is @reactiff/dcs and the executable name is dcs. This release does not publish to npm.

Use

npx dcs init
dcs check
dcs status
dcs next
dcs doctor

dcs init safely installs the v2 runtime under .dcs/ and creates .dcs/dcs-setup-for-chatgpt.zip. dcs upgrade migrates a recognized v1 installation transactionally, preserving its ledger and project history. Host application files are not moved or overwritten.

The initial ledger is a valid bootstrap/unplanned state. check, status, and next therefore succeed immediately and report that planning is required rather than assuming an application tree exists.

Planning handoff

Upload .dcs/dcs-setup-for-chatgpt.zip to ChatGPT with the project idea. ChatGPT should populate product, architecture, roadmap/milestones, acceptance/evidence, constraints, authorization, and .dcs/spec/implementation.json, then return dcs-setup-for-project.zip.

The returned project ZIP is a project-specific payload only. Its expected entries are .dcs/project/README.md, .dcs/project/product.md, .dcs/project/architecture.md, .dcs/project/roadmap.md, .dcs/project/acceptance.md, .dcs/project/constraints.md, .dcs/project/authorization.md, and .dcs/spec/implementation.json. Extract it at the project root after review. It must not contain the DCS runtime, application code, secrets, or build output.

Export from the reference checkout

From the reference checkout:

node scripts/export-dcs.mjs
cd .dcs-release
npm pack

The generated .dcs-release/ directory is ignored and is not part of the reference checkout commit.