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

@prisma_labs/atlas

v0.1.3

Published

Repo-owned evidence toolkit for canonical product surfaces.

Vulnerabilities

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

Links

Git

Maintainers

safronov.iliasafronov.ilia

Keywords

Readme

Atlas

Atlas is a repo-owned evidence toolkit for canonical product surfaces.

Published consumer package:

  • @prisma_labs/atlas

It is built for two first-class users:

  • agents that need a cheap machine-readable index of screens, flows, and provenance
  • humans that need a static browser of the product without manually running the app

Wave 1 modules:

  • core schema, run-report contract, promotion/sweep lifecycle, provenance, drift
  • ui static canonical screen evidence
  • flow multi-step journey evidence, keyframes, contact sheets, poster frames, raw video/log refs
  • viewer-react reusable browser for dense gallery browsing and relationship tracing
  • cli stable commands for validation, render, promotion, sweep, and viewer build

This repo is the authoritative home for Atlas contracts, architecture, and adoption docs. Consumer repos keep only app-specific registry entries, capture wrappers, generated outputs, and operational policy.

Start here:

Preferred local commands:

bun install
bun run atlas:bootstrap
bun run atlas:test:core
bun run atlas:test:viewer-graph
bun run atlas:test:viewer-helpers
bun run atlas:test:viewer-build
bun run atlas:test
bun run atlas:validate
bun run atlas:render-index
bun run atlas:build-viewer
bun run atlas:publish -- --bump patch --dry-run
bun run check

Consumer install:

npm install --save-dev @prisma_labs/atlas

Consumer repos should depend on the published package by default. Use this repo as the source of truth for Atlas development, contracts, docs, and releases.

Deterministic publish flow:

bun run atlas:publish -- --bump patch --dry-run
bun run atlas:publish -- --bump patch
bun run atlas:publish -- --version 0.2.0

The publish script enforces:

  • clean worktree
  • main checked out
  • HEAD == origin/main before bumping
  • bun run check
  • npm pack --dry-run
  • committed release version, matching git tag, npm publish, and registry verification

Viewer source of truth:

  • atlas/viewer/src/
  • atlas/viewer/dist/ is generated output and must not be edited directly
  • consumer repos should rebuild viewer assets instead of patching bundled dist files by hand

Primary env/config surface:

  • ATLAS_PROJECT_ROOT
  • ATLAS_ROOT
  • ATLAS_VIEWER_SRC_ROOT
  • ATLAS_VIEWER_TITLE
  • ATLAS_VIEWER_DESCRIPTION
  • ATLAS_DEVICE_INSTALL_SCRIPT
  • ATLAS_SKIP_PUSH_CHECK

Atlas assumes consumer registry entries provide captureCommand values that emit the run-report JSON contract consumed by the promotion and sweep scripts.

For device-sensitive flows, Atlas also ships:

  • scripts/observe-device-flow.sh
  • scripts/install-connected-devices.sh as a placeholder adapter

Consumer repos are expected to provide or override the device installer with app-specific logic.