Repository navigation
v0.1.3
v0.1.3
OIDC Trusted Publishing for PyPI (canonprims) and npm (@3leaps/canonprims),
published-release staging and live registry digest verification, and
release-script portability hardening. The library, language bindings,
conformance corpus and canon command are unchanged from 0.1.2.
What it ships
- Rust crates
canonprims-coreandcanonprims-json(crates.io). - Go module
github.com/3leaps/canonprims(packagecanon), standard
library only and cgo-free. canoncommand for linux amd64/arm64, darwin arm64 and windows
amd64/arm64.- Python package
canonprims(PyPI): an abi3 wheel per platform for
CPython 3.10 and later, on linux amd64/arm64 (manylinux2014, glibc 2.17 or
later), darwin arm64 and windows amd64/arm64. No source distribution. - npm package
@3leaps/canonprims: one WebAssembly module with no
imports, embedded in an ES module with no runtime dependencies. Tested on
Node.js 20 and 22.
The wheels and the npm package are release assets: built and tested in the
tag workflow, listed in both checksum manifests and covered by both
signatures. The packages on PyPI and npm are these exact files.
Release machinery and OIDC publication
.github/workflows/registry-publish.yml: manualworkflow_dispatch
workflow on av*tag ref. Theverifyjob restores and verifies the
signed tag onorigin, checks source inertness, stages and verifies the
published GitHub release viascripts/release-stage-published.sh, and
uploads the verified release bundle. Thepublish-pypi(publish-pypi
environment) andpublish-npm(publish-npmenvironment) jobs re-verify
every wheel and tarball SHA-256 against the signedSHA256SUMSmanifest
(scripts/ci-prepare-pypi-publish.sh,scripts/ci-publish-npm-oidc.sh),
publish via OIDC Trusted Publishing with PEP 740 and npm provenance
attestations, and runscripts/release-verify-registries.sh.- Live registry and provenance verification (
make release-stage-published,make release-verify-registries):
binds staged public signing keys, fingerprint pins and release notes
byte-for-byte to the verified tag commit, verifies bothSHA256SUMSand
SHA512SUMSsignatures, and confirms that PyPI serves the exact five wheels
under.ownership.organization == "3leaps"with PEP 740 provenance
attestations (/integrity/canonprims/<version>/<wheel>/provenance) and npm
serves the exact@3leaps/canonprimstarball (dist.integritySHA-512 SRI
anddist.shasum) with Sigstore provenance (dist.attestations.provenance). - GitHub environment, ruleset, and signing ceremony guards: adds
scripts/release-github-preflight.sh(make release-github-preflight) to
verify thepublish-pypiandpublish-npmenvironments (required reviewer +
v*tag policy), theTag Publish Protectionruleset, and
immutable_releases; pinsgit -c gpg.format=openpgp -c gpg.program=gpg -c gpg.openpgp.program=gpgfor tag signing and verification; refuses the
default~/.gnupgkeyring during signing; and updates
scripts/release-prepare-tag-message.pyto the 3-line attribution trailer. - Portability and ceremony helpers: adds
make release-stage,
make release-crates-cleanandmake release-pack-npm-redirector, declares
npm(>= 10.0.0) anduv(>= 0.5.0) in.goneat/tools.yamland
config/doctor-versions.txt, enforces lowercase-only ASCII hex in the Rust
canon-diffcrosscheck driver, guards against unguarded Bash 3.2 empty-array
expansions inscripts/jq-portability.sh, uses mode-120000git index
entries andcore.autocrlf=falsein the surface-check test suites, and
separates project name and trademark notices intoNOTICEalongside verbatim
LICENSE-MITandLICENSE-APACHEfiles in the repository root and binding
packages.
Conformance
- Corpus
conformance/canonical-json/v0, 180 cases, unchanged.
MANIFEST.jsonsha256:
de3ac543580ddb90f7e3a6e72239097274d3635ea783f302a9260b5a7d0c8d90. - Rust and Go agree byte for byte on the corpus and on generated input:
crosscheck seeds20261022and20261023, 5000 inputs each, on every
native CI cell. - Each binding runs the whole corpus against its installed package (the
wheel, or the packed npm tarball), and its corpus results and its output on
the same crosscheck seeds equal Rust's byte for byte.
Verification
canon canonicalizes and digests; it verifies no signatures, so it embeds no
key. To verify this release, check the signed tag v0.1.3 and the signed
checksum manifests against the public pins committed in the tagged commit
(docs/security/); see docs/security/README.md. A wheel or the npm tarball
downloaded from PyPI or npm has the SHA-256 listed for it in SHA256SUMS.