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

@spoolis/outcome

v0.1.2

Published

Verify signed Spoolis Outcome Receipts offline.

Readme

Outcome receipt verification

An Outcome Receipt is the signed record of what passed the agreed acceptance policy and what was earned.

Install

npm install @spoolis/outcome

Verify offline

Fetch the published keys once, select and pin the trust entry your application accepts, then store it with your application:

const keys = await fetch('https://spoolis.com/.well-known/spoolis-keys.json')
  .then((response) => response.json())

const trustEntry = keys.receipts.production.find(
  (entry) => entry.key_id === 'your-approved-key-id',
)

// Persist trustEntry in your application configuration before going offline.

After pinning the entry, verification makes no network calls:

import { readFile } from 'node:fs/promises'
import { verifyOutcome } from '@spoolis/outcome'

const receipt = JSON.parse(await readFile('outcome-receipt.json', 'utf8'))
const trustSet = [pinnedTrustEntry]

const result = await verifyOutcome(receipt, {
  trustSet,
  environment: 'production',
})

The caller supplies the trust set. This package does not fetch or broaden it.

Verification is offline by default. When a consumer must not act on a superseded receipt, fetch its current status and require that source:

// fetchReceiptStatus is re-exported from @spoolis/receipt-verifier and throws
// on a network or malformed response; an undefined status source makes
// require_current fail closed with status_source_required.
const status = await fetchReceiptStatus('https://spoolis.com', receipt.id).catch(() => undefined)
const gate = await requireOutcome(receipt, { minimum_status: 'pass', require_current: true }, { trustSet, statusSource: status })

CLI

npx -y @spoolis/cli outcome verify outcome-receipt.json

Read the Outcome Receipt documentation or inspect the Outcome Receipt schema.