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

aitri

v0.4.0

Published

<p align="center"> <img src="assets/aitri-avatar.png" alt="Aitri Header" width="250" /> </p>

Downloads

95

Readme

What Is Aitri

Aitri is a command-line SDLC engine that enforces disciplined, spec-driven execution for AI-assisted development. It helps teams move from user requirements to verified software through explicit workflow gates and human approvals.

Core operating model:

  • Spec first, implementation second.
  • Requirements are user-authored: Aitri structures and validates; it does not invent requirements.
  • Traceability by default: FR -> US -> TC.
  • Runtime verification required before handoff.
  • Human go/no-go decisions are mandatory.
  • Agents operate through explicit commands and gates.

Why Teams Use Aitri

  • Reduce drift in AI-generated workflows.
  • Keep decisions and artifacts auditable over time.
  • Maintain continuity across sessions with checkpoint/resume.
  • Standardize delivery quality in terminal-native workflows.

SDLC Flow Enforced by Aitri

draft -> approve -> discover -> plan -> validate -> verify -> policy -> handoff -> go

This flow is deterministic and designed to block ambiguous or weak transitions.

Requirements

  • Node.js >=18
  • Git (recommended for checkpoint and resume workflow)

Installation

git clone https://github.com/cesareyeserrano/aitri.git
cd aitri
npm i -g .
hash -r
aitri --version

Quick Start

Initialize a target project:

mkdir -p ~/Documents/PROJECTS/my-feature
cd ~/Documents/PROJECTS/my-feature
aitri init
aitri resume

Run the baseline SDLC workflow (interactive default):

aitri draft --feature user-login --idea "Email/password login"
aitri approve --feature user-login
aitri discover --feature user-login
aitri plan --feature user-login
aitri validate --feature user-login --format json
aitri verify --feature user-login --format json
aitri policy --feature user-login --format json
aitri handoff

Automation/CI mode (optional): use --non-interactive --yes only when you explicitly need unattended execution.

Check state at any point:

aitri status --json

Generate a static status page:

aitri status --ui

Use --no-open if you only want file generation.

Command Reference

| Command | Purpose | | --- | --- | | aitri init | Initialize baseline project structure | | aitri draft | Create a draft specification from idea input | | aitri approve | Run draft quality gates and move spec to approved | | aitri discover | Produce discovery artifact and initial scaffolding | | aitri plan | Generate plan, backlog starter, and test-case starter | | aitri validate | Validate traceability and placeholder resolution | | aitri verify | Execute runtime verification and persist evidence | | aitri policy | Run managed policy checks before implementation handoff | | aitri status | Show current state and recommended next command | | aitri resume | Continue deterministically from checkpoint context | | aitri handoff | Present handoff status for explicit human decision | | aitri go | Enter implementation mode after successful handoff | | aitri help | Show command and option reference |

Common flags:

  • --non-interactive (automation/CI only)
  • --yes (automation/CI only)
  • --feature <name>
  • --json / --format json
  • --verify-cmd "<command>"
  • --guided

Skill Adapters

Aitri ships skill adapters for terminal-first AI coding environments:

  • Codex: adapters/codex/SKILL.md
  • Claude: adapters/claude/SKILL.md
  • OpenCode: adapters/opencode/SKILL.md

Codex local install:

mkdir -p ~/.codex/skills/aitri
cp adapters/codex/SKILL.md ~/.codex/skills/aitri/SKILL.md

Documentation

Primary references:

  • Docs index: docs/README.md
  • Getting started: docs/guides/GETTING_STARTED.md
  • Execution rules: docs/EXECUTION_GUARDRAILS.md
  • Strategy: docs/STRATEGY_EXECUTION.md
  • Progress checklist: docs/PROGRESS_CHECKLIST.md
  • File growth policy: docs/guides/FILE_GROWTH_POLICY.md
  • Checkpoint/resume runbook: docs/runbook/SESSION_CHECKPOINT_AND_RESUME.md
  • Skill packaging guide: docs/guides/SKILL_PACKAGING_AND_INSTALL.md

Contributor Validation

npm run test:smoke
npm run test:regression
npm run check:file-growth
npm run check:file-growth:strict
npm run demo:5min

Project Status

Aitri is actively maintained with a CLI-first focus and deterministic workflow gates.

License

  • License: Apache-2.0 (LICENSE)
  • Attribution: NOTICE