@asphalt-react/helper
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:helmet | AI (typosquat): Scoped design-system package; Levenshtein match to 'helmet' is a false positive with no brand impersonation intent. | ai | |
| phantom-deps | phantom-dep:text-encoder-lite | AI (phantom-deps): Declared runtime dep used in browser bundle config; phantom-dep heuristic fires because it's not directly imported in source. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.15.0 | 2 / 3 | |
| 2.14.0 | 2 / 3 | |
| 2.13.0 | 2 / 3 | |
| 2.12.0 | 2 / 3 | |
| 2.10.0 | 2 / 3 |
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.