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

@pathos-labs/dacs-fixtures

v0.1.0

Published

Deterministic data-only C1, settlement, and HTLC fixtures for DACS interoperability

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

pathos-labspathos-labs

Keywords

Readme

@pathos-labs/dacs-fixtures

A deterministic, data-only package of PATH-OS C1 materials and settlement/HTLC fixtures for implementations that do not clone this repository.

This package is not a DACS-Standard publication. It includes non-normative PATH-OS material and byte-for-byte copies of the pinned inputs identified below.

Contents and origins

| Packaged file | Group | Upstream path | Repository and pin | | --- | --- | --- | --- | | data/c1/conformance/implementation-manifests/pathos-dacs-ref.json | c1 | conformance/implementation-manifests/pathos-dacs-ref.json | cX3po/pathos-dacs-ref | | data/c1/conformance/partner-kit/LICENSE | c1 | conformance/partner-kit/LICENSE | cX3po/pathos-dacs-ref | | data/c1/conformance/partner-kit/MANIFEST.json | c1 | conformance/partner-kit/MANIFEST.json | cX3po/pathos-dacs-ref | | data/c1/conformance/partner-kit/README.md | c1 | conformance/partner-kit/README.md | cX3po/pathos-dacs-ref | | data/c1/conformance/partner-kit/vectors.json | c1 | conformance/partner-kit/vectors.json | cX3po/pathos-dacs-ref | | data/c1/docs/c1-conformance-bridge.md | c1 | docs/c1-conformance-bridge.md | cX3po/pathos-dacs-ref | | data/htlc/conformance/security-vectors/convergence-harness/corpus/attestation-bundle-htlc9.json | htlc | conformance/security-vectors/convergence-harness/corpus/attestation-bundle-htlc9.json | cX3po/pathos-dacs-ref | | data/settlement/conformance/security-vectors/sb2-settlement-uniqueness/vectors/sb2-settlement-uniqueness-v0.1.json | settlement | conformance/security-vectors/sb2-settlement-uniqueness/vectors/sb2-settlement-uniqueness-v0.1.json | cX3po/pathos-dacs-ref | | data/settlement/conformance/security-vectors/settlement-v1/vectors/settlement-v1-v0.1.json | settlement | conformance/security-vectors/settlement-v1/vectors/settlement-v1-v0.1.json | cX3po/pathos-dacs-ref | | data/settlement/dacs-standard/README.md | settlement | test/fixtures/dacs-standard-63793a39/README.md | cX3po/pathos-dacs-ref | | data/settlement/dacs-standard/fixtures/settlement-evidence-delivery-success.json | settlement | conformance/fixtures/settlement-evidence-delivery-success.json | https://github.com/DACS-Agent-commerce/DACS-Standard @ 63793a39 | | data/settlement/dacs-standard/fixtures/settlement-evidence-payment-success.json | settlement | conformance/fixtures/settlement-evidence-payment-success.json | https://github.com/DACS-Agent-commerce/DACS-Standard @ 63793a39 | | data/settlement/dacs-standard/vectors/security/bundle-settlement-evidence-bijection-v0.4.json | settlement | conformance/vectors/security/bundle-settlement-evidence-bijection-v0.4.json | https://github.com/DACS-Agent-commerce/DACS-Standard @ 63793a39 |

The two settlement-named security-vector sets included from conformance/security-vectors are settlement-v1 and sb2-settlement-uniqueness; no other directory name there contains settlement or htlc. The HTLC convergence corpus file is included separately because it is an explicitly selected fixture.

The packaged data/settlement/dacs-standard/README.md is the PATH-OS pin record for the copied DACS-Standard files. It records source fixture hashes and the short commit pin 63793a39; it is not the upstream DACS-Standard README. The C1 implementation manifest and partner-kit manifest also retain their own embedded provenance pins.

The top-level LICENSE reproduces the PATH-OS MIT notice and the DACS-Standard MIT notice from DACS-Standard commit 63793a39. NOTICE maps packaged files to the applicable notice.

Index

index.json is JCS-canonical JSON with version pathos-dacs-fixtures-index:0.1. generatedFrom.sourceManifestSha256 hashes the JCS list of source paths and content hashes, so it is independent of the checkout's current commit. Top-level pins names only the upstream DACS-Standard and dacs-sdk commits already recorded by the copied sources. Each files entry gives a package-relative path, SHA-256, byte count, group, and origin. Each expectations entry is copied only from a vector's own case-level expected, verdict, or decision field; vectorName is the case's name or id when present. Files without such a field have no expectation entry.

To verify the bytes, hash a data file directly and compare both values with its index entry, for example:

sha256sum data/settlement/conformance/security-vectors/settlement-v1/vectors/settlement-v1-v0.1.json

wc -c data/settlement/conformance/security-vectors/settlement-v1/vectors/settlement-v1-v0.1.json

From a checkout of the source repository, rebuild or check the complete package with:

node --import tsx scripts/build-fixtures-package.mts

node --import tsx scripts/build-fixtures-package.mts --check