← Home

@pie-element/ebsr

A [pie][pie] ebsr component.

6
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ed.eustaceelodszoposlakatosandreievaneuschilleniousandreeapescarcarlacosteaiacoshoriajustinheuer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): SLSA provenance attestation via Sigstore confirms legitimate CI/CD publish; mitigates account-takeover risk. ai
npm-metadata no-description AI (npm-metadata): Empty description is a known pattern across all @pie-element/* packages; not a malware indicator. ai
phantom-deps phantom-dep:classnames AI (phantom-deps): classnames is declared in package.json dependencies; phantom-dep heuristic false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
14.2.2 6 / 0
14.2.1 6 / 0
14.1.0 6 / 0
14.0.1 6 / 0
14.0.0 6 / 0
12.3.3 6 / 0

v14.2.2

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.

v14.2.1

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.

v14.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.

v14.0.1

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.

v12.3.3

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.