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

@arch-atlas/core

v0.1.8

Published

AST scanner and architecture graph engine

Readme

@arch-atlas/core

AST scanner and architecture graph engine for Arch Atlas.

Version: 0.1.8

Most users should install the CLI:

npm install -D arch-atlas
npx arch-atlas

Use this package directly when you want to embed scanning in a custom tool, script, or CI helper without the web UI.

Install

npm install @arch-atlas/core

Requires Node.js >= 18.

Quick start

import { scanProject, getImpactTree, analyzePackageBoundaries } from '@arch-atlas/core';

const graph = await scanProject(
  { root: '/path/to/project' },
  (progress) => console.log(progress.message),
);

console.log(graph.stats);
console.log(graph.deadCode[0]?.explanation); // why unused
console.log(graph.packageBoundaries.deepImports);

const impact = getImpactTree(graph, graph.files[0].id, 3);

Main exports

| API | Purpose | |-----|---------| | scanProject(options, onProgress?) | Full scan → ArchitectureGraph | | discoverProject(root) | Project type, entries, aliases, workspaces | | detectDeadCode(files, entries, type?) | Unused files with explanation.checks | | getDependencyTree(graph, fileId, depth?) | Forward import tree | | getImpactTree(graph, fileId, depth?) | Reverse dependents (“what breaks?”) | | analyzePackageBoundaries(files) | Cross-package / deep-import report | | detectCircularDependencies(files, edges) | Cycle list | | loadIgnoreMatcher(root) | Defaults + .arch-atlasignore |

The graph includes nodes, edges, files, deadCode, circularDependencies, packageBoundaries, packages, routes, folders, searchIndex, and config.

Dead-code explanations

Each DeadCodeItem includes:

explanation: {
  summary: string;
  importerPaths: string[];
  checks: Array<{
    id: 'entry' | 'framework-route' | 'reachable' | 'importers' | 'platform-sibling';
    label: string;
    ok: boolean;
    detail?: string;
  }>;
}

Runtime reachability ignores import type / export type. Platform siblings (.ios, .android, …) stay live when the base module is reachable.

Accuracy notes (v0.1.8)

  • Entries from package.json main / react-native / module, Expo entryPoint, app.config.*, Next middleware
  • React.lazy(() => import('…')) and require.context('…') when the argument is a string literal
  • Barrel re-exports (export … from) count toward reachability
  • Type-only imports do not create runtime graph edges

Fixtures & tests

npm run test -w @arch-atlas/core

Fixtures live under packages/core/fixtures/ (Expo Router, Next.js, RN CLI, monorepo).

Related packages

License

MIT