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

spectra-pack

v3.0.7

Published

CLI operating system for AI-assisted product development

Vulnerabilities

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

Links

Git

Maintainers

yunus.akinyunus.akin

Keywords

aiclideveloper-toolsevalsgovernanceproduct-developmentrelease-confidencespectraspec-driventelemetryverification

Readme

spectra-pack

spectra-pack installs the spectra CLI.

Spectra is a CLI-first operating system for AI-assisted product development. It bootstraps project-local context, business knowledge, executable specs, staged approvals, eval contracts, telemetry contracts, semantic diff checks, role-aware context packs, and release-confidence verification.

Install

New project:

npx spectra-pack@latest init my-product
cd my-product
./spectra/bin/spectra check
./spectra/bin/spectra status

Existing project:

cd existing-project
npx spectra-pack@latest adopt .
./spectra/bin/spectra status
./spectra/bin/spectra check

npx bootstraps the repository but does not create a global command. Continue with ./spectra/bin/spectra, or install the standalone native binary for a global spectra command.

Node/npm-free macOS and Linux installation is documented in Native Install.

Commands

The examples below use spectra. Replace it with ./spectra/bin/spectra when using only the repo-local launcher.

Setup:

spectra init [path] [--profile <lite|full>] [--git-mode <local|shared>]
spectra adopt [path] [--profile <lite|full>] [--git-mode <local|shared>]

Workflow:

spectra context --role planner --goal discover
spectra task --item TASK-001 --task-type feature --goal "Describe intended change"
spectra check
spectra status
spectra update

Utilities:

spectra help
spectra help advanced
spectra admin doctor
spectra admin diff semantic

What It Installs

Spectra initializes a repository by creating one Spectra-owned directory:

  • spectra/bin/ repo-local launcher
  • spectra/install.json profile, Git mode, CLI/runtime version, and schema metadata
  • spectra/docs/ generated Spectra reference material
  • spectra/sdd/ profile runtime, working context, and business memory

Spectra-owned files should not be installed into root-level docs/, sdd/, .spectra/, .github/, or app/. Legacy shell scripts may still exist in the repository for compatibility and runtime maintenance, but the supported consumer setup path is this CLI.

Lite is the default. Full adds executable specs, governance, adoption, agent adapters, and advanced admin workflows. Local Git mode is the default and excludes /spectra/ through .git/info/exclude; shared mode makes it commit-ready.

Business Context

Business knowledge lives under spectra/sdd/memory-bank/business/ and is indexed by domain. Context routing uses domain names, related modules, and explicit configured keywords to include only task-relevant business rules and unresolved questions, which keeps prompts smaller while preserving durable project knowledge.

| Domain | Keywords | Rules | Unresolved | Related Modules |
| --- | --- | --- | --- | --- |
| customer-policy | eligibility,limit,approval | business/customer-policy/rules.md | business/customer-policy/unresolved.md | account-service |

spectra route --format json explains each match with fields such as domainMatches and moduleMatches.

New business claims default to unresolved. Use --status active --verified only when evidence is authoritative; code behavior alone should normally be recorded as unresolved.

Agent adapters such as AGENTS.md or CLAUDE.md are generated only when requested with a Full profile. They point agents back to the same Spectra source of truth instead of duplicating project knowledge per agent.

Documentation

License

MIT