@asphalt-react/selection
Selection component is a family of components which allows users to choose option(s) from a list of items.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal Gojek DLS package; provenance not configured for this monorepo, consistent across all versions. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally proprietary Gojek internal component; UNLICENSED is expected and stable. | ai | |
| dependencies | unvetted-dep:@asphalt-react/helper | AI (dependencies): Sibling package in the same Gojek DLS monorepo; unvetted status is a pipeline gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@asphalt-react/iconpack | AI (dependencies): Sibling package in the same Gojek DLS monorepo; unvetted status is a pipeline gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@asphalt-react/textfield | AI (dependencies): Sibling package in the same Gojek DLS monorepo; unvetted status is a pipeline gap, not a risk signal. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.15.2 | 12 / 3 | |
| 2.15.0 | 12 / 3 | |
| 2.5.1 | 13 / 3 | |
| 2.4.0 | 13 / 3 |
v2.15.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (antoniomontana) than the most recent previously approved version (elayudhanira-gojek) on 2026-05-25, but antoniomontana is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.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.