← Home

@pie-lib/tools

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ed.eustacelakatosandreichilleniousandreeapescarcarlacosteaiacoshoriajustinheuer

Keywords

reactpietools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:assert AI (phantom-deps): assert is declared as a runtime dep and referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@emotion/react AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai
phantom-deps phantom-dep:@emotion/style AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai
phantom-deps phantom-dep:@mui/icons-material AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai

Versions (showing 3 of 3)

Version Deps Published
2.0.2 12 / 3
2.0.1 12 / 3
2.0.0 12 / 3

v2.0.2

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.

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