react-colorful
🎨 A tiny (2,8 KB) color picker component for React and Preact apps. Fast, well-tested, dependency-free, mobile-friendly and accessible
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 | obfuscated-file:dist/index.mjs | AI (source-diff): dist/index.mjs is a documented build artifact (postbuild copies index.module.js to index.mjs). Content is minified React color picker code, not obfuscated malware. Stable for this package. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 5.7.0 | 0 / 30 | |
| 5.6.2 | 0 / 30 | |
| 5.6.1 | 0 / 30 | |
| 5.6.0 | 0 / 30 | |
| 5.5.1 | 0 / 30 | |
| 5.5.0 | 0 / 28 | |
| 5.4.0 | 0 / 28 | |
| 5.3.1 | 0 / 28 | |
| 5.3.0 | 0 / 28 | |
| 5.2.3 | 0 / 28 | |
| 5.2.2 | 0 / 28 | |
| 5.2.1 | 0 / 28 | |
| 5.2.0 | 0 / 28 | |
| 5.1.4 | 0 / 28 | |
| 5.1.3 | 0 / 28 | |
| 5.1.2 | 0 / 27 | |
| 5.1.1 | 0 / 27 | |
| 5.1.0 | 0 / 27 | |
| 5.0.1 | 0 / 27 | |
| 5.0.0 | 0 / 28 | |
| 4.4.4 | 0 / 27 | |
| 4.4.3 | 0 / 27 | |
| 4.4.2 | 0 / 27 | |
| 4.4.1 | 0 / 27 | |
| 4.4.0 | 0 / 27 | |
| 4.3.0 | 0 / 27 | |
| 4.2.0 | 0 / 27 | |
| 4.1.4 | 0 / 27 | |
| 4.1.3 | 0 / 27 | |
| 4.1.2 | 0 / 27 | |
| 4.1.1 | 0 / 27 | |
| 4.1.0 | 0 / 27 | |
| 4.0.7 | 0 / 27 | |
| 4.0.6 | 0 / 27 | |
| 4.0.5 | 0 / 27 | |
| 4.0.4 | 0 / 27 | |
| 4.0.3 | 0 / 27 | |
| 4.0.2 | 0 / 27 | |
| 4.0.1 | 0 / 27 | |
| 4.0.0 | 0 / 27 | |
| 3.0.3 | 0 / 27 | |
| 3.0.2 | 0 / 26 | |
| 3.0.1 | 0 / 26 | |
| 2.3.1 | 0 / 28 | |
| 2.3.0 | 0 / 28 | |
| 2.2.1 | 0 / 22 | |
| 2.2.0 | 0 / 22 | |
| 2.1.2 | 0 / 21 | |
| 2.1.1 | 0 / 21 | |
| 2.1.0 | 0 / 21 | |
| 2.0.3 | 0 / 21 |
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.