← Home

@pie-element/passage

npm Repository Homepage

Renders passage content.

5
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 confirms legitimate CI/CD publish; no material changes from prior version. ai
phantom-deps phantom-dep:@emotion/react AI (phantom-deps): Declared as a runtime dep; phantom-dep heuristic fires on config-only references, stable false positive for this package. ai
phantom-deps phantom-dep:@emotion/style AI (phantom-deps): Same pattern as @emotion/react; config-only reference, stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Part of a large, long-lived monorepo (pie-framework/pie-elements); sparse README is typical for internal element packages. ai

Versions (showing 5 of 5)

Version Deps Published
7.1.2 10 / 0
7.1.1 10 / 0
7.0.1 10 / 0
7.0.0 10 / 0
5.3.3 8 / 0

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

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

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

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