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

@project-surface/adapter-sdk

v0.2.0

Published

Contract and conformance harness for project-surface adapters.

Readme

@project-surface/adapter-sdk

The contract every project-surface adapter implements, plus the conformance suite that proves it.

An adapter implements detect and extract, gets read-only file access through its context, and proposes claims - commands, capabilities, evidence, environment - each carrying a provenance tier and at least one source. It can never execute anything.

import { assertConformance } from "@project-surface/adapter-sdk";

await assertConformance(myAdapter, "fixtures/my-fixture");

The conformance suite enforces what every consumer relies on:

  • every claim names a source file and an honest tier (derived or inferred),
  • no absolute or machine-specific path leaks into the output,
  • statically discovered evidence is never reported as passed,
  • two runs over the same project produce byte-identical output.

The same suite runs as a command, for adapters that live outside the project-surface repository:

npx -p @project-surface/adapter-sdk surface-conform ./dist/index.js fixtures/my-fixture

Exit 0 conforms, 2 a check failed (each is printed with its detail), 1 the module is not an adapter.

Also exported: claim builders, contract-document discovery (findContracts) and toolchain probes (isOnPath) that check for a binary without running it.

Read docs/adapters.md before writing one.