@asphalt-react/icontuner
Icontuner
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@asphalt-react/helper | AI (dependencies): Internal Gojek design system sibling dep; stable pattern across all @asphalt-react/* packages. | ai | |
| dependencies | unvetted-dep:@gojek/asphalt-web-tokens | AI (dependencies): Internal Gojek design token package; consistent with the design system monorepo pattern. | ai | |
| dependencies | unvetted-dep:@asphalt-react/svg-normalizer | AI (dependencies): Internal Gojek design system sibling dep; stable pattern across all @asphalt-react/* packages. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.15.1 | 4 / 4 | |
| 2.15.0 | 4 / 4 | |
| 2.14.0 | 4 / 4 | |
| 2.12.2 | 4 / 4 | |
| 2.11.0 | 4 / 4 | |
| 2.10.0 | 4 / 4 | |
| 2.9.0 | 4 / 4 | |
| 2.8.1 | 4 / 4 | |
| 2.8.0 | 4 / 4 | |
| 2.6.0 | 4 / 4 |
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.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.