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

@daihum/scholar-contract

v0.1.4

Published

DAIHUM Scholar neutral OPERATION CONTRACT: a machine-readable operation manifest (scholar.operation-manifest.v1) + per-op JSON Schemas, authored in zod, emitted as a deterministic JSON bundle (scholar.operation-bundle.v1) that Carrel's generic generator a

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

bo.anbo.an

Keywords

scholaroperation-contractjson-schemacarrelauto-derivationdaihum

Readme

@daihum/scholar-contract

The neutral Scholar operation contract — a machine-readable manifest of Scholar operations + per-op JSON Schemas, authored in zod and emitted as a deterministic JSON bundle. Carrel's generic generator ingests the bundle and auto-derives its CLI/descriptors/authority — no hand-written downstream TypeSpec ("doc folding", zero manual maintenance). zod is the ergonomic authoring face; the emitted JSON Schema is the vendor-neutral truth (same pattern as @daihum/work-metadata).

Exports (cleanly split — the data path pulls no impl deps)

  • @daihum/scholar-contract/operation-bundle.v1.json — the canonical data asset Carrel ingests at codegen. Pure JSON (scholar.operation-bundle.v1): envelope + manifest + first-party I/O schemas (keyed by $id, linked $refs) + externalSchemas (work.v1). Deterministic, content-hashed.
  • @daihum/scholar-contract/operation-bundle — the same bundle as a typed loader (operationBundle).
  • @daihum/scholar-contract — types, zod schemas, the manifest, assembleBundle().
  • @daihum/scholar-contract/handlers — createScholarOperationHandlersV1(deps): a THIN, dependency-injected handler registry keyed by opId. Each handler delegates to an injected port or fails closed with a typed reason. The real execution lives in the host (the extension's download executor; a node/provider resolve engine) — this is a SEAM, not an authority path.

First slice

scholar/record.resolve@v0 (read control) · scholar/item.download@v0 · scholar/batch.download@v0 (the two download ops are browser-required; node/daemon fails closed; batch is a durable job).

Build

pnpm --filter @daihum/scholar-contract build → tsdown then scripts/gen-bundle.mjs writes the deterministic operation-bundle.v1.json. A test guards: the on-disk bundle == source, the zod schemas == the runtime types (drift), and work.v1's $id == @daihum/work-metadata's.

Versioning

op-id @vN is the consumer contract (breaking I/O → @v(N+1), coexisting); scholar.operation-manifest.v1 is the envelope; additive-within-@vN. Per-schema + bundle sha256 content hashes for compatibility/readback.