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

@zachscodingstream/engine

v0.0.1

Published

Core code intelligence engine with free CLI adapter

Readme

@zachcodingstream/engine

Core code intelligence engine with a lightweight CLI adapter.

Parse, index, and query relationships between functions, symbols, and files in JavaScript and TypeScript projects.


INSTALLATION

Install Globally (CLI)

npm install -g @zachcodingstream/engine

Then run:

zcs-cli

Install Locally (Library Usage)

npm install @zachcodingstream/engine


CLI USAGE

Ingest a File

zcs-cli ingest path/to/file.js

Ingest a Folder

zcs-cli ingest path/to/project/

Supported Extensions:

  • .js
  • .ts
  • .jsx
  • .tsx
  • .py

Query a Symbol

zcs-cli query MyFunction

Returns:

  • Symbol details
  • Callers
  • Callees
  • Related symbols in the same file

Lifecycle Commands

zcs-cli lifecycle clear zcs-cli lifecycle reset zcs-cli lifecycle rebuild

clear → clears runtime relationships reset → wipes entire project index rebuild → rebuilds from snapshot


PROGRAMMATIC USAGE

Example:

const projectIndex = require("@zachcodingstream/engine/core/projectIndex"); const fileParser = require("@zachcodingstream/engine/core/fileParser");

const content = "..."; const parsed = fileParser.parseFile("example.js", content); projectIndex.upsertFile("example.js", parsed);


ARCHITECTURE

The engine is separated into layers:

core/ projectIndex.js fileParser.js queryHandler.js

adapters/ cli/

  • core contains all business logic
  • adapters expose that logic externally
  • no business logic lives in the CLI

This allows future adapters such as:

  • HTTP APIs
  • Desktop applications
  • Editor integrations
  • Remote indexing services

VERSIONING

Current version: 0.0.1

This project is in early development. Breaking changes may occur before 1.0.0.


LICENSE

MIT © ZachCodingStream

See LICENSE file for full text.


CONTRIBUTING

Pull requests and improvements are welcome.

If you build something interesting with the engine, feel free to share.