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

@bodanglin/verdict-contracts

v0.3.0

Published

Canonical Zod schemas and TypeScript types for Verdict v1 contracts

Readme

@bodanglin/verdict-contracts

Canonical Zod schemas and TypeScript types for Verdict v1 contracts.

ExecutionEnvelope v1 Contract

The ExecutionEnvelope is Verdict's canonical execution contract from verdict-core to Node and Cockpit consumers. Each envelope contains all information needed for execution within Verdict-approved boundaries without requiring callbacks to Core for eligibility decisions. Fields include:

  • task_spec: Task description and metadata
  • eligibility_decision: Admission status
  • routing_decision: Optional routing metadata
  • policy_digest: SHA-256 hex digest (64 lowercase hex characters, no prefix)
  • allowed_capabilities: Permitted capability identifiers
  • evidence_ids: Referenced evidence identifiers
  • execution_constraints: Hard constraints including expires_at (bounded lifetime)
  • verification_requirements: Required verification checks and plans
  • created_at: Optional envelope creation timestamp
  • schema_version: Contract version identifier (currently "1")

Verdict verifiers parse the envelope, validate the schema (rejecting unknown fields), check eligibility, verify the policy digest matches the expected policy, and enforce time-bounded execution via expires_at. If all checks pass, the verifier returns ACCEPT; otherwise, it returns DENY, EXPIRED, DIGEST_MISMATCH, or REJECT_UNKNOWN.

Full semantics: docs/contracts/EXECUTION_ENVELOPE_V1.md

Fixtures: Canonical Test Vectors

This package ships sha256-pinned test fixtures for ExecutionEnvelope v1:

  • fixtures/execution-envelope/v1/: Six canonical test cases (accepted.json, denied.json, expired.json, null-defaults.json, unknown-field.json, wrong-digest.json) with expected verdicts and sha256 digests in manifest.json.
  • fixtures/execution-envelope/v1-mutations/: A mutation corpus (cases.json) for Python/Zod validation parity, sha256-pinned by manifest.json.

Loading a fixture:

import manifest from '@bodanglin/verdict-contracts/fixtures/execution-envelope/v1/manifest.json' with { type: 'json' };

// Or with createRequire (for older Node or CommonJS):
import { createRequire } from 'module';
const require = createRequire(import.meta.url);
const manifest = require('@bodanglin/verdict-contracts/fixtures/execution-envelope/v1/manifest.json');

The manifest lists each fixture file, its expected verdict, and its sha256 digest. Verify fixture integrity by hashing the file and comparing to the manifest.

Versioning

This package follows 0.x.y versioning: minor bumps (0.2→0.3) may break backward compatibility. Pin your dependency or test after updates.

Node Engines

Requires Node ≥18.

License

MIT