@asphalt-react/date-picker
DatePicker
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): Stable pattern for this package; no provenance across 60 versions. | ai | |
| dependencies | unvetted-dep:@asphalt-react/context | AI (dependencies): Sibling package in the same Gojek/Asphalt React monorepo. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Private corporate design system; UNLICENSED is intentional and consistent across the org. | ai | |
| dependencies | unvetted-dep:@asphalt-react/iconpack | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@asphalt-react/button | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@asphalt-react/toggle-button | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@asphalt-react/textfield | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@asphalt-react/helper | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@asphalt-react/popover | AI (dependencies): Same-org monorepo sibling; not an independent supply-chain risk. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.15.2 | 9 / 3 | |
| 2.15.1 | 9 / 3 | |
| 2.15.0 | 9 / 3 | |
| 2.14.0 | 9 / 3 | |
| 2.12.0 | 10 / 3 | |
| 2.11.0 | 10 / 3 | |
| 2.9.0 | 10 / 3 | |
| 2.8.1 | 10 / 3 | |
| 2.8.0 | 10 / 3 | |
| 2.6.0 | 10 / 3 | |
| 2.5.0 | 10 / 3 | |
| 2.4.0 | 10 / 3 | |
| 2.3.0 | 10 / 3 | |
| 2.1.0 | 10 / 3 | |
| 2.0.2 | 10 / 3 | |
| 2.0.1 | 10 / 3 | |
| 2.0.0 | 10 / 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.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.2
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.