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

@archora/core

v2.1.0

Published

Framework-independent analyzer core for Archora. Builds the dependency model, detects cycles, computes metrics and recommendations from any FileSource. No Vue, Pinia or Tauri dependencies.

Downloads

612

Readme

@archora/core

Framework-independent analyzer core for Archora. Builds a dependency graph from TypeScript and Vue source files, detects cycles, computes per-module metrics, flags FSD layer violations, and evaluates user-declared architectural contracts.

No Vue, Pinia, or Tauri dependencies. Runs in Node.js, in a Web Worker, or inside the Tauri desktop app.

Install

npm install @archora/core

Usage

import { runAnalysis } from '@archora/core';
import { NodeFsFileSource } from '@archora/core/analyzer/sources/nodeFsFileSource';
import { loadFrontScopeConfig } from '@archora/core/config';

const source = new NodeFsFileSource('/path/to/project');
const config = await loadFrontScopeConfig('/path/to/project');
const result = await runAnalysis(source, config);

console.log(result.graph.cycles.length, 'cycles found');

For most use cases prefer the CLI — @archora/cli wraps this package and handles argument parsing, output formatting, and CI exit codes.

What it computes

  • Dependency graph — parses .ts, .tsx, .js, .jsx, .vue (and .svelte, beta), resolves tsconfig path aliases including recursive alias→alias chains
  • Dynamic & framework-auto edgesimport(), React.lazy, next/dynamic, Vue/Nuxt component and Nuxt composables/ auto-imports
  • Cycles — Tarjan's SCC; classifies as direct (length ≤ 2) or indirect
  • Per-module metrics — fan-in, fan-out, instability, depth, coupling, hotness score
  • Layer violations — FSD-style rules (shared → entities → features → widgets → pages → app)
  • Contract checks — boundary rules, package budgets, API stability, bundle thresholds from .archora.json
  • RSC boundary leaks — server/client runtime from directives, server-only/client-only packages and framework conventions; flags client → server imports, direct and transitive
  • Bundle signals — duplicated modules, heavy chunks, solo-hot modules, barrel tree-shaking leaks (from webpack/rollup stats)
  • Temporal coupling — modules that change together without a static edge (from git log), ranked by risk

FileSource

FileSource is the only IO seam — swap implementations to run the analyzer in any environment:

| Implementation | Environment | |---|---| | NodeFsFileSource | Node.js / CLI | | BrowserFsFileSource | Browser (File System Access API) | | TauriFsFileSource | Tauri desktop | | MemoryFileSource | Tests, Web Worker payload |

Analyzer pipeline

discoverFiles → parseFiles → resolveImports → buildGraph
              → detectCycles → computeMetrics → rankHotZones → ScanResult

License

Apache-2.0 — free for any use, including commercial and CI.