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

@intentius/tsad-reference

v2.1.0

Published

The reference implementation of the typescript-as-data specification, written from the specification text and nothing else.

Readme

@intentius/tsad-reference

A reference implementation of the specification in spec/, written from the specification text and nothing else (#50).

What it implements, and what it does not

Implemented: shape classification, expression evaluation (J1), the per-file verdict and the identity-taint fixpoint (J2, J3, since #60), revival through a host's real constructors (F-Val-Fate, since #64), and the host interface's registry, helper allowlist, owned-specifier prefixes and values. It declares the specification version it implements (specVersion on its adapter), and the suite holds that to spec/VERSION.

Not implemented, with the reason for each: CAVEATS.md. F-Call step 6, invoking a project module in open mode, is the one thing a fixture cannot ask of it.

As a package

@intentius/tsad-reference depends on @intentius/tsad-conformance for the adapter and host types only. Its major and minor are the specification version it implements; the patch is its own.

Provenance

From #19 until #50 these files were a port of chant's, kept current by a sync script and a list of recorded cuts. That guaranteed agreement and made agreement uninformative: the cross-check was comparing the same code with itself. #50 replaced the ported evaluation layer with one written from the specification text.

One honest limit on how independent that is. The author of the rewrite had previously read chant's implementation closely, while writing the specification from it. The rewrite was done from grammar.md and judgments.md without consulting the source, but it is not the test a reader who had never seen chant would constitute. What it does establish is that the specification text is complete enough to implement from, and it found one place where it was not: spec/grammar.md's definition of an unclaimed callee, which four normative sentences used and none defined (#51).

The cut list and the sync script are in git history at the commit that removed them, as the record of what the host interface was derived from.