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

@dtmd/temper

v0.0.7

Published

The temper authoring face — the six-noun model as typed modules: harness(), kind<T>(), clause values, needs, and file()/text/blocks(). Emit compiles to the declaration rows the engine reads, a byte-faithful projection, and the lock.

Downloads

1,061

Readme

temper-sdk — the authoring face

The typed module library the ratified corpus names as temper's authoring medium (specs/intent.md; specs/model/pipeline.md, "The SDK"). A harness author composes members as typed values in the six-noun model; emit compiles the whole into the declaration rows the engine reads, a byte-faithful .claude/** projection, and the lock. The SDK implements no semantics — every type erases at the seam, and the engine consumes only declared data, offline, no Node.

The six-noun face

  • harness() — the assembly as one typed value: members · expect · require · settings (specs/model/pipeline.md, "The SDK").
  • kind<T>() — the engine room: a kind is a typed constructor plus five facts of runtime residue (label, locus, layout, registration, edge fields — specs/model/representation.md). The built-in Claude Code kinds rule / skill / memory are ordinary kind<T>() values; an embedded child kind is the same constructor at the embedded locus.
  • Clause valuesclause(predicate, { severity, guidance, cite }) over the closed predicate algebra (required, maxLines, …); a floor is an exported clause array, adopted by spread in expect (specs/model/contract.md).
  • needs — the capabilities a member uses (bash("git diff")); emit derives the permission union, so a permission is never authored twice.
  • file() / text`…` / blocks() — the three prose constructors, one field type; the author's words land byte-identical to their authored text.

What emit produces

One deterministic pass over the harness, double-emit verified (specs/model/pipeline.md, "Emit"):

  • Declaration rows — the erased program (kind facts, clauses, requirements, assembly facts) on the internal versioned JSON pipe and in the lock's [declaration] families, byte-matching the Rust lock shape (src/drift.rs) — the byte-parity lockstep two writers keep until single-writer lands.
  • A byte-faithful projection — each rule / skill / memory member compiled whole to its .claude/** locus; install's placement lines round-trip.
  • The lock — rollup provenance/emit fingerprints plus the declaration rows.

Emit is total (members are the only source), refuses before it writes on a broken source (a dangling satisfies, an unfilled required, an unresolved mention), and is byte-reproducible. writeEmit lands the lock and the projection on disk; the JSON pipe is in-flight, not a committed artifact.

Stated bounds — each a named follow-on, never silently faked

  • The permission union is carried as data — the fold into the settings artifact lands with the hook/MCP kinds it folds many-to-one.

Tests

pnpm --dir sdk testtsc (the keystroke wall) then node --test, including projection byte-parity and lock fingerprints against real Rust output, and the declaration-row byte shape against the Rust [declaration] families.