@pie-lib/icons
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is confirmed by SLSA provenance attestation; legitimate automation change. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): MUI ecosystem peer dep; referenced in config files as documented pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package in pie-framework org; Levenshtein match to 'cors' is a false positive. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Config-only reference in a MUI icon library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@emotion/style | AI (phantom-deps): Config-only reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mui/icons-material | AI (phantom-deps): Config-only reference in an icon library; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 5 / 1 | |
| 4.0.2 | 5 / 1 | |
| 4.0.1 | 5 / 1 | |
| 4.0.0 | 5 / 1 | |
| 0.1.0 | 6 / 0 |
v4.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-06-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.