← Home

c15t

9
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

burnedchris

Keywords

consentprivacygdprccpalgpdtcfiabcmpconsent-managementconsent-management-platformcookie-bannercookie-consentcookiesconsent-bannerconsent-managerpreference-centerheadlessjavascripttypescriptssrserver-side-renderingtracking-consenteu-cookie-law

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance attestation; consistent with automated release pipeline adoption. ai
provenance slsa-provenance AI (provenance): Package consistently published via CI with Sigstore attestation; stable supply chain signal. ai
provenance no-provenance AI (provenance): Established package with public GitHub repo; lack of Sigstore attestation is common and not a risk signal here. ai
phantom-deps phantom-dep:@orpc/server AI (phantom-deps): @orpc/server is a declared runtime dep used in config/type references; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@orpc/client AI (phantom-deps): @orpc/client is a declared runtime dep used in config/type references; phantom-dep heuristic false positive for this package. ai
dependencies unvetted-dep:@c15t/schema AI (dependencies): First-party scoped dep from same c15t monorepo; stable false positive for this package. ai
dependencies unvetted-dep:@c15t/translations AI (dependencies): First-party scoped dep from same c15t monorepo; stable false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
2.1.0 3 / 4
2.0.4 3 / 4
2.0.0 3 / 4
1.8.6 5 / 4
1.8.5 5 / 4
1.8.3 5 / 4
1.8.2 5 / 4
1.8.1 5 / 4
1.8.0 5 / 4

v2.1.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.

v2.0.4

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.

v2.0.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.

v1.8.6

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.

v1.8.5

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.

v1.8.3

2 findings
HIGH Publisher changed: burnedchris → GitHub Actions (on 2026-01-19) provenance

This version was published by a different npm account than previous versions on 2026-01-19. This could indicate a legitimate maintainer transition or an account compromise.

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.

v1.8.2

2 findings
HIGH Publisher changed: burnedchris → GitHub Actions (on 2025-12-12) provenance

This version was published by a different npm account than previous versions on 2025-12-12. This could indicate a legitimate maintainer transition or an account compromise.

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.

v1.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.