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

@agenticprimitives/provenance-node

v0.0.0-alpha.25

Published

Node-side reference bindings of the provenance ports (spec 414 §5): the W3C RDFC-1.0 canonicalizer, SHACL validation over the published run shapes, a directory store, and the `ap conform provenance` suite (C1–C6) any binding is run through.

Readme

@agenticprimitives/provenance-node

Part of Agentic Primitives — the open-source trust substrate for agentic applications: identity that can sign, authority checked at act time, evidence the owner carries. Developer kit · All packages

The Node-side reference bindings of the provenance ports, and the conformance suite that proves a store binding keeps a run's record intact.

A run's provenance is a W3C PROV-O / P-Plan / EP-Plan graph in JSON-LD; its measurements are W3C DQV. Where those records are KEPT — an agent's vault, a directory of files, a Solid pod, a Graph Store — is a binding of one port. ap conform provenance runs any binding through six checks and prints what it broke:

| | Check | | --- | --- | | C1 | a record put and got back has the same RDFC-1.0 digest (the graph, not the bytes) | | C2 | every predicate and class IRI in it is declared in the published ontology; Turtle is served from it | | C3 | it conforms to the published SHACL shapes as returned, and a twin still fails | | C4 | it carries no words (no address, no body; a measurement is a number) | | C5 | an absent record is absent; a reader without standing is refused — never served empty | | C6 | a rollup wiped and rebuilt from the records gives the same numbers |

ap conform provenance file:./eval-store     # a directory of .jsonld files
ap conform provenance memory:               # the in-memory reference

In code: runProvenanceConformance(store, { stranger, rollup }) for any ProvenanceStorePort — the vault binding in apps/demo-a2a is run through the same suite in its tests.

Also exported: rdfcCanonicalizer (for recordDigest), validateQuads (SHACL over the published shapes with the subclass closure materialized), toTurtle, and fileProvenanceStore.

Node only. A Worker bundles the zero-dependency @agenticprimitives/provenance and never this package.