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

@vxnus/e

v0.1.4

Published

Portable knowledge-pack and provider contract for Siduri

Downloads

1,037

Readme

@vxnus/e

The portable knowledge contract for Siduri. It defines pack identity, versioning, sources, documents, revisions, retrieval, and optional structured entities and relations.

E does not provide a database engine. Publishers may implement KnowledgeProvider over any storage or transport.

validateManifest(value) validates the serialized manifest.json boundary. It rejects unknown fields, requires a semantic pack version, uses an independent MAJOR.MINOR schema version, and returns actionable issues.

The canonical JSON Schema is published at schema/manifest.schema.json; the fixtures in fixtures/ are the conformance starting point. When semanticSearch is enabled, a manifest must declare the public embedding profile (model, dimensions, and provider). This describes compatibility only; credentials never belong in the manifest.

Retrieval uses validateRetrievalRequest() and validateRetrievalResponse(). Requests support lexical, semantic, and hybrid modes with a limit from 0 through 1000. Every returned result must include a revision and at least one source citation. assertConformantProvider() checks these rules and deterministic repeated retrieval for any provider.