rc-time-picker
React TimePicker
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 | publisher-changed | AI (provenance): Publisher change (afc163 → yesmeck) occurred in 2017 and reflects a settled, legitimate maintainer transition within the react-component org. yesmeck has a strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yesmeck was added as maintainer in 2017 as part of the same legitimate transition; stable for this package going forward. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence of attestation is expected for packages of this age and is a low-severity informational signal only. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 3.7.3 | 6 / 7 | |
| 3.7.2 | 6 / 7 | |
| 3.7.1 | 5 / 7 | |
| 3.7.0 | 5 / 7 | |
| 3.6.6 | 5 / 7 | |
| 3.6.5 | 5 / 7 | |
| 3.6.4 | 4 / 7 | |
| 3.6.3 | 4 / 7 | |
| 3.6.2 | 4 / 7 | |
| 3.6.1 | 4 / 7 | |
| 3.6.0 | 4 / 7 | |
| 3.5.0 | 4 / 7 | |
| 3.4.0 | 5 / 9 | |
| 3.3.1 | 5 / 9 | |
| 3.3.0 | 5 / 9 | |
| 3.2.1 | 5 / 9 | |
| 3.2.0 | 5 / 9 | |
| 3.1.0 | 5 / 9 | |
| 3.0.0 | 5 / 9 | |
| 2.4.1 | 5 / 10 | |
| 2.4.0 | 5 / 9 | |
| 2.3.5 | 5 / 9 | |
| 2.3.4 | 5 / 9 | |
| 2.3.3 | 4 / 10 | |
| 2.3.2 | 4 / 10 | |
| 2.3.1 | 4 / 10 | |
| 2.3.0 | 4 / 10 | |
| 2.2.2 | 4 / 10 | |
| 2.2.1 | 4 / 10 | |
| 2.2.0 | 4 / 10 | |
| 2.1.0 | 4 / 10 | |
| 2.0.2 | 4 / 10 | |
| 2.0.1 | 4 / 10 | |
| 2.0.0 | 4 / 10 | |
| 1.1.6 | 4 / 11 | |
| 1.1.5 | 4 / 11 | |
| 1.1.4 | 4 / 11 | |
| 1.1.3 | 4 / 11 | |
| 1.1.1 | 4 / 11 | |
| 1.1.0 | 4 / 11 | |
| 1.0.0 | 4 / 11 | |
| 0.7.2 | 5 / 10 | |
| 0.7.1 | 5 / 10 | |
| 0.7.0 | 5 / 10 | |
| 0.6.0 | 5 / 10 | |
| 0.5.6 | 6 / 10 | |
| 0.5.5 | 6 / 10 | |
| 0.5.4 | 6 / 10 | |
| 0.5.3 | 6 / 10 | |
| 0.5.2 | 6 / 10 | |
| 0.5.1 | 6 / 10 | |
| 0.5.0 | 6 / 10 | |
| 0.4.0 | 6 / 10 | |
| 0.3.3 | 6 / 10 | |
| 0.3.2 | 6 / 10 | |
| 0.3.1 | 6 / 10 | |
| 0.3.0 | 6 / 10 | |
| 0.2.0 | 6 / 10 |
v3.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-30. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-22. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-12-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsThis version was published by a different npm account than previous versions on 2017-11-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-22. This could indicate a legitimate maintainer transition or an account compromise.
v2.4.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-27. This could indicate a legitimate maintainer transition or an account compromise.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-11. This could indicate a legitimate maintainer transition or an account compromise.
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. Consider requesting the maintainer enable provenance via CI/CD.