rc-color-picker
color-picker ui component for react
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/rc-color-picker.js | AI (source-diff): Standard Webpack UMD bundle for a React UI component. The 'network+exec' pattern is webpack's module loader calling require('react')/require('react-dom') — not malicious. | ai | |
| source-diff | net-exec-file:dist/rc-color-picker.min.js | AI (source-diff): Minified Webpack UMD bundle — same pattern as the unminified dist file. Standard build artifact for a React component library. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is entirely explained by addition of dist/ build artifacts (212KB JS, 92KB minified JS, source maps) — expected for a component library adding UMD distribution files. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from yiminghe to noyobo occurred in 2016 as part of a legitimate react-component org transition. noyobo is a long-standing trusted contributor with strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (noyobo, shepherdwind) added in 2016 as part of the same legitimate org transition. Both are established contributors in the react-component ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected and not a risk signal for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.2.6 | 5 / 6 | |
| 1.2.5 | 5 / 8 | |
| 1.2.4 | 5 / 8 | |
| 1.2.3 | 5 / 8 | |
| 1.2.2 | 5 / 8 | |
| 1.2.1 | 5 / 8 | |
| 1.2.0 | 5 / 8 | |
| 1.1.7 | 5 / 8 | |
| 1.1.6 | 4 / 8 | |
| 1.1.5 | 4 / 8 | |
| 1.1.4 | 3 / 8 | |
| 1.1.3 | 3 / 8 | |
| 1.1.2 | 3 / 7 | |
| 1.1.1 | 3 / 7 | |
| 1.1.0 | 3 / 7 | |
| 1.0.1 | 3 / 7 | |
| 1.0.0 | 3 / 7 |
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
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-07-01. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.6
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-06-30. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.5
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-20. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2016-07-11. 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.
v1.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.