@asphalt-react/popover
Popover
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Gojek design system monorepo; no provenance is consistent across all @asphalt-react/* packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.15.3 | 5 / 2 | |
| 2.15.2 | 5 / 2 | |
| 2.15.1 | 5 / 2 | |
| 2.15.0 | 5 / 2 | |
| 2.12.2 | 6 / 2 | |
| 2.11.0 | 6 / 2 | |
| 2.10.0 | 6 / 2 | |
| 2.9.0 | 6 / 2 | |
| 2.8.1 | 6 / 2 | |
| 2.8.0 | 6 / 2 | |
| 2.6.0 | 6 / 2 | |
| 2.5.0 | 6 / 2 | |
| 2.4.0 | 6 / 2 | |
| 2.3.0 | 6 / 2 | |
| 2.1.0 | 5 / 2 | |
| 2.0.1 | 5 / 2 | |
| 2.0.0 | 5 / 2 |
v2.15.3
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 (elayudhanira-gojek) than the most recent previously approved version (antoniomontana) on 2026-07-07, but elayudhanira-gojek 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.3.0
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 (elayudhanira-gojek) than the most recent previously approved version (yessyprmtsr) on 2025-04-11, but elayudhanira-gojek 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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.