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

@fungi.computer/issues

v0.2.0

Published

Pure validation and metadata projection for a complete issue tree

Readme

Issues

inspectIssueTree(files) validates a complete issues/ tree supplied as a record of relative paths and Markdown text. It returns typed diagnostics, summaries, the unblocked frontier, and metadata-only records. Any invalid ticket makes records empty; callers can retain their previous valid projection. Filesystem discovery, Git access, commit identity and persistence belong to the caller. Repository tooling supplies the local filesystem adapter.

The single frontmatter contract lives in src/issue-schema.ts. VFile Matter owns YAML extraction, Effect validates JSON values, @cfworker/json-schema applies the contract (no code generation, so it runs in Workers and under a strict CSP), and remark parses Markdown headings. Heading comparisons retain literal inline Markdown; fenced code does not supply required sections. The blocker walk is iterative, so dependency depth does not consume the JavaScript call stack.

This recovers the validator and projection from c83b1098c06c90e6ab9a74c0f11bcefab6b15ae4 with current parser and Effect dependencies. Queued immutable-commit reads, last-good persistence and Grove indexing remain separate tracker work.

import { inspectIssueTree } from "@fungi.computer/issues";

const { records, diagnostics } = inspectIssueTree({});
// An empty tree has no records or diagnostics.

Packed consumer readiness

Run pnpm run build, pnpm run pack and pnpm run stranger in this package. The maintained stranger proof installs only package tarballs into a fresh npm consumer, checks the exact shipped files, runs the public runtime fixture and compiles every JavaScript entrypoint with strict NodeNext and no library-check skip. This qualification does not publish npm releases or push a repository split.

See LICENSE for the license and the package manifest for its public repository destination.

Quick start

import { inspectIssueTree } from "@fungi.computer/issues";

const { records, diagnostics } = inspectIssueTree({});
console.log({ records, diagnostics });

Core concepts

The caller supplies a complete tree snapshot. Invalid tickets produce diagnostics and no accepted records; filesystem discovery and persistence remain with the caller.

Examples and checks

The packed runtime fixture at test/stranger/runtime.mjs exercises the public API in a fresh consumer. Run pnpm run stranger after building the package.

Install

Install the package tarball with npm. The manifest pins its runtime dependencies.

Contribute and license

See LICENSE for the MIT terms.