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

@didwork/sdk

v0.1.0

Published

DidWork: independent verification for software outcomes. Your software said it worked. Did it?

Readme

@didwork/sdk

Your software said it worked. Did it?

DidWork independently verifies that the outcomes software claims to have produced are actually true. Send a claim; DidWork gathers evidence from authoritative systems and returns a verdict: verified, failed, or unknown.

import { did } from "@didwork/sdk";

const result = await did.verify({
  type: "stripe.refund",
  expected: { payment: "pi_123", amount: 4999 },
});

if (result.status === "verified") proceed();

Configure with DIDWORK_API_KEY (get one at didwork.sh), or explicitly via createClient({ apiKey }). Zero dependencies.

Capability Trust

Declare what an agent tool is allowed to affect. did.tool() is local and synchronous: it attaches the declaration and rejects effects outside the DidWork taxonomy, so a typo cannot become an under-declaration.

export const refundCustomer = did.tool({
  name: "refund_customer",
  description: "Refund an existing customer charge.",
  effects: ["financial.refund", "communication.external"],
  constraints: { maxAmount: 500 },
});

npx @didwork/inspect inspect compares declarations like this against the implementation and reports a DECLARATION_MISMATCH when the code exceeds them. Pass the tools that did a piece of work to did.verify({ tools }) and the receipt records what they could affect, kept apart from the evidence and never an input to the verdict:

await did.verify({
  type: "stripe.refund",
  expected: { payment: "pi_123", amount: 4999 },
  tools: [refundCustomer],
});

The taxonomy (CAPABILITIES), risk table (CAPABILITY_RISK), and profile types are exported for tooling.

Docs: https://didwork.sh/docs