@asphalt-react/flag
Flag
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 |
|---|---|---|---|---|
| license | uncommon-license:UNLICENSED | AI (license): Intentional UNLICENSED status for internal component; consistent across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Gojek monorepo package; no provenance is consistent across all versions of this org's packages. | ai | |
| dependencies | unvetted-dep:@asphalt-react/context | AI (dependencies): Internal sibling dep from same @asphalt-react monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@asphalt-react/button | AI (dependencies): Internal sibling dep from same Gojek design system monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@asphalt-react/svg-normalizer | AI (dependencies): Internal sibling dep from same Gojek design system monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@asphalt-react/helper | AI (dependencies): Internal sibling dep from same Gojek design system monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@asphalt-react/iconpack | AI (dependencies): Internal sibling dep from same Gojek design system monorepo; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.15.1 | 6 / 3 | |
| 2.15.0 | 6 / 3 | |
| 2.12.1 | 7 / 3 | |
| 2.12.0 | 7 / 3 | |
| 2.11.0 | 7 / 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.12.1
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.