verifiable-delivery-packager
Deterministic software-delivery packaging with integrity manifests, executable-bit auditing and cryptographic review receipts.
| Size | Folder | Inside |
|---|---|---|
| 9.7 kB | src/ | 3 source files |
| 2.4 kB | examples/ | 1 example |
| 5.3 kB | tests/ | 1 test file |
| 17.7 kB | (root) | 14 docs · 3 config files |
| Size | Path |
|---|---|
| 30 B | .gitignore |
| 1.2 kB | AGENT_EVAL.md |
| 602 B | ARCHITECTURE.md |
| 328 B | CHANGELOG.md |
| 407 B | DEPENDENCIES.md |
| 1.7 kB | LICENSE.md |
| 319 B | LIMITATIONS.md |
| 1.7 kB | PREVIEW.md |
| 996 B | QUICKSTART.md |
| 3 kB | README.md |
| 556 B | SECURITY.md |
| 701 B | SUPPORT.md |
| 885 B | TEST_REPORT.md |
| 216 B | THIRD_PARTY_NOTICES.md |
| 838 B | THREAT_MODEL.md |
| 154 B | VERIFICATION.md |
| 1.2 kB | commercial-manifest.json |
| 2.4 kB | examples/package-demo.mjs |
| 663 B | package.json |
| 2.3 kB | release-manifest.json |
| 1.7 kB | src/index.d.ts |
| 230 B | src/index.mjs |
| 7.8 kB | src/packager.mjs |
| 5.3 kB | tests/delivery.test.mjs |
Already bought this?
View your purchasesREADME
Verifiable Delivery Packager
Cryptographic delivery packaging, tamper-evident manifest generation, and verifiable review receipts for AI agent and CI/CD deliverables.
1. WHAT IS THIS?
The Verifiable Delivery Packager is a zero-dependency Node.js library for engineering teams, autonomous AI agent pipelines, and automated review platforms. It bundles software deliverables into deterministic, tamper-evident packages backed by canonical JSON manifests and cryptographically signs review decisions via verification receipts.
2. WHO IS IT FOR?
- AI Agent Framework Developers: Requiring strict boundaries, canonical manifests, and cryptographic certainty before committing agent changes.
- Security & Compliance Teams: Enforcing verifiable audit trails for automated code generation.
- CI/CD Pipeline Engineers: Ensuring artifact integrity between build, test, review, and deployment stages.
3. WHAT PROBLEM DOES IT SOLVE?
Autonomous agents produce files dynamically. Traditional tarballs or git commits do not provide deterministic canonicalization, leave vulnerabilities open to permission escalation (executable bits), and lack decoupled cryptographic review receipts that can prove an auditor approved the exact byte-for-byte deliverable without re-running the entire repository history.
4. WHY PAY FOR IT INSTEAD OF BUILDING IT?
- Deterministic Canonical Serialization: Recursively sorts object keys to guarantee identical JSON manifests produce identical SHA-256 digests across platforms.
- Strict Executable Bit Auditing: Verifies that no deliverable file possesses executable permissions (
mode & 0o111 === 0), eliminating surprise script execution vectors. - Path Traversal & Symlink Immunity: Automatically detects and rejects symlinks, absolute paths, null bytes, and traversal sequences (
..). - Decoupled Verification Receipts: Generates cryptographic review approval records (
DELIVERY_RECEIPT.json) bound to package digests. - Zero External Dependencies: Built entirely on Node.js built-in modules (
node:crypto,node:fs,node:path).
5. WHAT IS VERIFIED?
- 7 / 7 Automated Unit Tests Passed: Canonical JSON sorting, end-to-end package generation and verification, unauthorized mutation detection, path traversal rejection, rogue extra file detection, executable bit set rejection, and symlink rejection.
- 100% Clean-Room Isolation: Verified passing inside clean temporary directory with zero network access and zero external npm packages.
6. HOW DO I RUN IT?
# 1. Run unit test suite
node --test tests/delivery.test.mjs
# 2. Run interactive delivery & receipt demo
node examples/package-demo.mjs
Security scan report
Scanned by X402 Git, OSV (opens in a new tab) and Socket (opens in a new tab) — passed on all three. Findings from Socket are listed below.
- secrets
- none found
- X402 Git
- size limits
- within caps
- X402 Git
- known malware
- no dependency manifests to check
- OSV
- known vulnerabilities
- no dependency manifests to check
- OSV
- dependency behaviour
- nothing on a direct dependency · 1 in transitive packages
- Socket
- instruction smuggling
- none found
- X402 Git
- what it can do
- nothing to declare
- X402 Git
What this can do
links to 1 host in its docs · nothing runs at install
Findings (1)
- LOWSocket SBOM Resolver — Socket SBOM Resolver (transitive) — no lockfile, so installs are not reproducible
Releases 1
- v1.0.02026-09-16
release: v1.0.0 commercial source edition