npm for verified code.
Every package carries a mathematical proof. Search, install, compose — never rewrite what's already proven. If the code changes one byte, the badge turns red.
[01] SEARCH
[02] FEATURED CIRCUITS
Pre-certified. Ready to use.
[03] PUBLISHING
From code to registry in minutes
Write & certify
Write your PCD circuit and run brikc check to verify Φ_c = 1.
Publish
Run brikc registry publish to push to the public or private registry.
Discover
Others search, browse, and install your circuit with full certification proof.
Verify
The badge is a live endpoint — if the code changes, the badge turns red instantly.
[04] BADGE SYSTEM
Live proof. Not a static label.
The badge in your README is a live endpoint — it queries the registry with the program's hash on every page load. If the deployed binary differs by a single byte, the badge immediately shows INVALID.
Hash in registry, all monomers verified
Every input path verified — produces a correct output or an explicit rejection per the circuit's specification.
Hash in registry, Core + Extended
Certified where Core, contracted at the boundary. The percentage shows Core monomer coverage.
Hash mismatch — code modified after certification
The program no longer matches the certified version. Even one byte of change triggers this.
What no other certification standard can claim
Publish your first circuit
Install the CLI, certify a function, and publish to the registry. Every certified circuit is a building block someone else never has to rewrite.