Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.
ZK-Verify is the supply-chain layer of the Agent-008 enterprise AI governance platform — every binary, package, and update an AI agent runs is proven authentic before it executes, catching the unlisted malware signature tools miss.
H33-ZK-Verify uses zero-knowledge proofs to verify every binary, package, and firmware update against the publisher's cryptographic commitment — before it runs. Not signature scanning. Mathematical proof.
Your CI pipeline says green. Your antivirus says clean. But one package — buried four levels deep — was published 3 days ago by an attacker.
npm install pulls 847 packages. Your CI pipeline says green. Your antivirus says clean. But one of those packages — buried four levels deep in the dependency tree — was published 3 days ago by an attacker. It has the right name, the right version, the right README. It passed every check. Because every check is looking for known-bad. Nobody proved it was known-good.
Every package is verified against the publisher's SHA3-256 commitment before it installs. If the hash doesn't match, it doesn't run. Not because it's known-bad. Because it isn't known-good. GlassWorm compromised 433 repos. ZK-Verify would have caught every one.
In March 2026, GlassWorm compromised 433 components across GitHub, npm, VSCode, and OpenVSX. It used invisible Unicode characters to hide malicious code in plain sight. It stored its C2 server address on the Solana blockchain — permanent, public, impossible to take down. It stole AWS keys, SSH keys, Docker credentials, and installed a Chrome extension that logged every keystroke. The developer didn't install it. Their IDE's package manager did.
Every compromised package would have failed ZK-Verify's publisher commitment check. Hash mismatch on injection. Blocked before execution.
Every install runs all 5 streams simultaneously. SHA3-256 commitments verify every claim. Zero-knowledge — nothing about your infrastructure is revealed.
From typosquatted packages to firmware rollbacks. Every technique that bypasses your CI pipeline — caught by proof.
ZK-Verify sits in your install pipeline. Every package, binary, and firmware update is proven authentic before it runs.
npm install, pip install, apt-get, firmware OTA — every install passes through verification first.Every stream completes before the package finishes downloading. Cache hits from DashMap resolve in 80 nanoseconds.
Every major supply chain attack in the last 5 years would have been blocked by a single check: does the hash match the publisher's commitment?
Start free. Scale as your pipeline grows. Every tier includes SHA3-256 zero-knowledge commitments.
| Tier | Volume | Price | Includes |
|---|---|---|---|
| Free | 1,000 checks/mo | $0 | Binary + publisher verification |
| Pro | 50,000 checks/mo | $49/mo | All 5 streams + supply chain |
| Business | 500,000 checks/mo | $299/mo | + firmware + priority + custom publishers |
| Enterprise | Unlimited | Custom | + on-prem + dedicated registry + SLA |
ZK-Proven verifies your connections. ZK-Phish verifies your content. ZK-Verify verifies your code. Together as ZK-Trustless, they cover every attack surface — from the network layer to the content layer to the supply chain.
Verify any package, binary, or firmware update with a single request. Results in microseconds.
ZK-Verify renders an independent verdict on an artifact that already exists — a binary, package, or firmware update — by reproducing its hash and checking it against the publisher’s cryptographic commitment. It is a consumer of the owned capability at Verification.
What a passing verdict means — and does not. A verdict of authentic means the artifact reproduces and matches the publisher’s commitment. It does not mean the software is secure, bug-free, well-designed, or compliant — only that the bytes you received are the bytes the publisher committed to. That boundary is what makes an independent verdict meaningful.
When to reach for something else. Use Verification (or ZK-Verify) for an independent verdict on an artifact that already exists. Use HATS for continuous operational evidence over time. Use HICS for a software or control maturity score. Use Agent-008 to govern whether an action was authorized. Use H33-74 to produce the portable evidence in the first place. ZK-Verify consumes an artifact; it does not monitor over time, score maturity, or govern the decision.
What does a passing verdict mean — and what does it NOT mean?
It means the artifact’s hash reproduces and matches the publisher’s SHA3-256 commitment — the bytes are what the publisher committed to. It does not mean the software is secure, correct, or compliant.
Is the verifier independent of H33?
Verification is against the publisher’s commitment, not H33’s say-so. The check is a zero-knowledge proof over a public commitment; the verdict rests on the artifact and the registered hash, not on trusting H33.
How is Verification different from HATS, HICS, and Agent-008?
Verification renders an independent verdict on an artifact that already exists. HATS records and monitors operational evidence over time; HICS scores maturity; Agent-008 governs the decision. ZK-Verify only reproduces and validates the artifact.
Does a hash match prove the code is safe to run?
No. A match proves the artifact is the one the publisher committed to — not that the publisher’s code is free of vulnerabilities. It closes the “is this really what they shipped?” gap, not the “is what they shipped good?” question.
1,000 free checks. No credit card.