@asphalt-react/time-picker
Picker to select & set a specific time
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/textfield | AI (dependencies): Same @asphalt-react monorepo; sibling dep pattern is stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Internal proprietary package; provenance not expected for this org's publishing workflow. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally proprietary/internal package; UNLICENSED is consistent across the @asphalt-react scope. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.15.2 | 10 / 3 | |
| 2.14.0 | 10 / 3 | |
| 2.12.0 | 11 / 3 | |
| 2.11.0 | 11 / 3 | |
| 2.8.1 | 11 / 3 | |
| 2.5.0 | 11 / 3 | |
| 2.4.0 | 11 / 3 |
v2.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.5.0
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.