@cerbos/core
Common types used by the Cerbos client libraries
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Coincides with CI/CD provenance migration; attestation covers integrity instead. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Move to org CI publisher with provenance, not a compromise. | ai | |
| dependencies | unvetted-dep:@cerbos/api | AI (dependencies): First-party sibling package in the same cerbos-sdk-javascript monorepo; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @cerbos/core is the official Cerbos SDK core package, not a typosquat of cors; scoped namespace and SLSA provenance confirm legitimacy. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 2 / 0 | |
| 0.31.0 | 2 / 0 | |
| 0.30.0 | 2 / 0 | |
| 0.29.0 | 2 / 0 | |
| 0.28.1 | 2 / 0 | |
| 0.28.0 | 2 / 0 | |
| 0.27.1 | 2 / 0 | |
| 0.27.0 | 2 / 0 | |
| 0.26.0 | 2 / 0 | |
| 0.25.2 | 2 / 0 | |
| 0.25.1 | 2 / 0 | |
| 0.25.0 | 2 / 0 | |
| 0.24.1 | 1 / 0 | |
| 0.24.0 | 1 / 0 | |
| 0.23.0 | 1 / 0 | |
| 0.22.0 | 1 / 0 | |
| 0.21.1 | 1 / 0 | |
| 0.21.0 | 1 / 0 | |
| 0.20.0 | 1 / 0 | |
| 0.19.0 | 1 / 0 | |
| 0.18.1 | 1 / 1 | |
| 0.18.0 | 1 / 1 | |
| 0.17.1 | 1 / 1 | |
| 0.17.0 | 1 / 1 | |
| 0.16.0 | 1 / 1 | |
| 0.15.0 | 1 / 1 | |
| 0.14.0 | 1 / 1 | |
| 0.13.0 | 1 / 1 | |
| 0.12.0 | 1 / 1 | |
| 0.11.0 | 1 / 1 | |
| 0.10.0 | 1 / 1 | |
| 0.9.1 | 1 / 1 | |
| 0.9.0 | 1 / 1 | |
| 0.8.1 | 1 / 0 | |
| 0.8.0 | 1 / 0 | |
| 0.7.1 | 1 / 0 | |
| 0.7.0 | 1 / 0 | |
| 0.6.0 | 1 / 0 | |
| 0.5.1 | 1 / 0 | |
| 0.5.0 | 1 / 0 |
v0.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cerbosdev.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (cerbosdev) than the most recent previously approved version (ahaines) on 2024-04-23, 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.
v0.17.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cerbosdev.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (cerbosdev) than the most recent previously approved version (ahaines) on 2024-04-17, 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.
v0.16.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ahaines.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.