@asphalt-react/modal
Modal
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): Internal Gojek design system; UNLICENSED is intentional for proprietary internal packages. | ai | |
| phantom-deps | phantom-dep:@asphalt-react/stack | AI (phantom-deps): @asphalt-react/stack is a same-org sibling dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.15.3 | 8 / 2 | |
| 2.15.2 | 8 / 2 | |
| 2.15.1 | 8 / 2 | |
| 2.15.0 | 8 / 2 | |
| 2.14.0 | 8 / 2 | |
| 2.13.0 | 8 / 2 | |
| 2.12.2 | 9 / 2 | |
| 2.11.0 | 9 / 2 | |
| 2.10.0 | 9 / 2 | |
| 2.9.0 | 9 / 2 | |
| 2.8.1 | 9 / 2 | |
| 2.8.0 | 9 / 2 | |
| 2.6.0 | 9 / 2 | |
| 2.5.0 | 9 / 2 | |
| 2.4.0 | 9 / 2 | |
| 2.1.0 | 8 / 2 | |
| 2.0.2 | 8 / 2 | |
| 2.0.1 | 8 / 2 | |
| 2.0.0 | 8 / 2 |
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
2 findingsPackage 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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.