← Home

@codaco/protocol-validation

npm Repository
17
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

jthrillybuckhalt

Versions (showing 17 of 17)

Version Deps Published
11.12.0 3 / 13
11.11.0 3 / 13
11.10.0 3 / 13
11.9.0 3 / 13
11.8.1 3 / 13
11.6.0 4 / 13
11.5.0 4 / 13
11.4.0 3 / 13
11.2.0 3 / 13
11.1.0 3 / 13
11.0.0 3 / 13
10.1.0 3 / 13
10.0.0 3 / 13
9.0.0 3 / 13
8.0.2 3 / 13
8.0.1 3 / 13
8.0.0 3 / 13

v11.12.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.11.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.10.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.9.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.8.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: jthrilly → GitHub Actions (on 2026-07-06, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (jthrilly) on 2026-07-06, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.