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

project-atlas

v0.1.4

Published

Project Atlas is a Git-first project knowledge base CLI for AI coding agents and reviewers.

Downloads

772

Readme

Project Atlas

Stop re-reading the whole repo. Start shipping with governed project knowledge.

English | 简体中文

Project Atlas is a Git-first project knowledge base CLI for engineering teams and AI coding agents. It keeps durable knowledge under knowledge/, turns updates into reviewable proposals, and requires a human terminal confirmation before any real write.

AI tools often re-read too much source, miss stable project facts, and leave teams with chat-only context. Project Atlas fixes that with governed repository knowledge, proposal-based updates, and a strict manual apply boundary.


Quick Start

Try the repository build:

npm install
npm run build
PROJECT_ATLAS_REPO="$PWD"
DEMO_REPO=/tmp/project-atlas-demo
mkdir -p "$DEMO_REPO"
cd "$DEMO_REPO"
git init
printf '# Demo Project\n\nThis repo demonstrates project-atlas.\n' > README.md
cat > updates.json <<'JSON'
{
  "source_files": ["README.md"],
  "updates": [
    {
      "target": "knowledge/project/overview.md",
      "content": "# Project Overview\n\nThis demo repository is used to verify Project Atlas.\n"
    }
  ]
}
JSON
node "$PROJECT_ATLAS_REPO/dist/index.js" init --repo "$DEMO_REPO" --template generic-service
node "$PROJECT_ATLAS_REPO/dist/index.js" context --repo "$DEMO_REPO" --query demo --budget 8000 --format json
node "$PROJECT_ATLAS_REPO/dist/index.js" propose --repo "$DEMO_REPO" --updates-file updates.json --reason "demo update"
node "$PROJECT_ATLAS_REPO/dist/index.js" review-summary --repo "$DEMO_REPO"

After npm publish, install the package and use the stable commands:

npm install -g project-atlas
project-atlas --help
project-atlas-mcp --help

One short flow gets you from repository setup to governed context and reviewable knowledge updates.


Why Project Atlas

Project Atlas is built for teams that want AI agents to reuse trusted project context instead of re-reading the entire repository on every task.

It helps teams:

  • store stable project knowledge in Git
  • keep knowledge tied to source files and hashes
  • review knowledge changes before they land
  • keep agent access read-oriented by default
  • capture durable project memory without turning chat logs into source of truth

How It Works

  • npm package: project-atlas
  • CLI command: project-atlas
  • Local stdio MCP server: project-atlas-mcp
  • Shared project knowledge directory: knowledge/
  • Local proposal evidence directory: .project-atlas/proposals/

The common sequence is simple:

  1. run init to create the knowledge base skeleton
  2. run context to read governed project context
  3. run propose or remember to create reviewable updates
  4. run review-summary before approval
  5. let a human run apply in a terminal

Project Atlas is not a hosted service and not a write-enabled agent plugin. It is a repository-native governance layer for project knowledge.


Core Safety Boundary

Agents may read context, inspect knowledge health, and create proposals.

Agents must not apply proposals.

Real writes still require a human terminal confirmation:

project-atlas apply --repo /path/to/repo --proposal-id <id> --confirm

The MCP server exposes safe tools only. There is no MCP apply tool.


Documentation

Choose a starting path:

Full documentation indexes:


Adapters And MCP

Project Atlas ships a local stdio MCP server and example adapters for agent tooling.

  • MCP server command: project-atlas-mcp
  • Example adapters: adapters/claude-code/, adapters/cursor/, adapters/continue/, adapters/opencode/

Use adapters for safe read and proposal workflows. Keep final apply in a human terminal session.


Contributing And Security