@strapi/plugin-color-picker
Strapi maintained Custom Fields
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): bassel17 is a plausible Strapi team addition; publisher track record is strong with no red flags. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Official Strapi monorepo plugin; publisher has strong track record and no material changes indicate a legitimate release. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a well-known React ecosystem package declared as a runtime dep; referenced in config files is a common pattern for React component libraries. | ai | |
| dependencies | unvetted-dep:@strapi/helper-plugin | AI (dependencies): First-party Strapi dependency used across the official Strapi monorepo; unvetted flag is a pipeline artifact, not a real risk for this package. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi monorepo pattern; LICENSE file exists in repository root. Stable for this package. | ai | |
| dependencies | unvetted-dep:@strapi/icons | AI (dependencies): @strapi/icons is an official first-party Strapi package; stable dependency for this plugin across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Strapi's official packages do not currently publish with Sigstore provenance; this is consistent across the entire Strapi ecosystem. | ai | |
| dependencies | unvetted-dep:@strapi/design-system | AI (dependencies): @strapi/design-system is an official first-party Strapi package; stable dependency for this plugin across all versions. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 4 / 8 | |
| 5.47.0 | 4 / 8 | |
| 5.46.1 | 4 / 8 | |
| 5.46.0 | 4 / 8 | |
| 5.45.1 | 4 / 8 | |
| 5.45.0 | 4 / 8 | |
| 5.44.0 | 4 / 8 | |
| 5.43.0 | 4 / 8 | |
| 5.42.1 | 4 / 8 | |
| 5.42.0 | 4 / 8 | |
| 5.41.1 | 4 / 8 | |
| 5.41.0 | 4 / 8 | |
| 5.40.0 | 4 / 8 | |
| 5.39.0 | 4 / 8 | |
| 5.38.1 | 4 / 8 | |
| 5.38.0 | 4 / 8 | |
| 5.37.1 | 4 / 8 | |
| 5.37.0 | 4 / 8 | |
| 5.36.1 | 4 / 8 | |
| 5.36.0 | 4 / 8 | |
| 5.35.0 | 4 / 8 | |
| 5.34.0 | 4 / 8 | |
| 5.33.4 | 4 / 8 | |
| 5.33.3 | 4 / 8 | |
| 5.33.2 | 4 / 8 | |
| 5.33.1 | 4 / 8 | |
| 5.33.0 | 4 / 8 | |
| 5.31.3 | 4 / 8 | |
| 5.31.2 | 4 / 8 | |
| 5.31.1 | 4 / 8 | |
| 5.31.0 | 4 / 8 | |
| 5.30.1 | 4 / 8 | |
| 5.30.0 | 4 / 8 | |
| 5.29.0 | 4 / 8 | |
| 5.28.0 | 4 / 8 | |
| 5.27.0 | 4 / 8 | |
| 5.26.0 | 4 / 8 | |
| 5.25.0 | 4 / 8 | |
| 5.24.2 | 4 / 8 | |
| 5.24.1 | 4 / 8 | |
| 5.24.0 | 4 / 8 | |
| 5.23.6 | 4 / 8 | |
| 5.23.5 | 4 / 8 | |
| 5.23.4 | 4 / 8 | |
| 5.23.3 | 4 / 8 | |
| 5.23.2 | 4 / 8 | |
| 5.23.1 | 4 / 8 | |
| 5.23.0 | 4 / 8 | |
| 5.22.0 | 4 / 8 | |
| 5.21.0 | 4 / 8 | |
| 5.20.0 | 4 / 8 | |
| 5.19.0 | 4 / 8 | |
| 5.18.1 | 4 / 8 | |
| 5.18.0 | 4 / 8 | |
| 5.17.0 | 4 / 8 | |
| 5.16.1 | 4 / 8 | |
| 5.16.0 | 4 / 8 | |
| 5.15.1 | 4 / 8 | |
| 5.15.0 | 4 / 8 | |
| 5.14.0 | 4 / 8 | |
| 5.13.1 | 4 / 8 | |
| 5.13.0 | 4 / 8 | |
| 5.12.7 | 4 / 8 | |
| 4.26.1 | 6 / 9 | |
| 4.26.0 | 6 / 9 |
v5.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.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.
v5.41.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.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.
v5.40.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.
v5.39.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.
v5.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.38.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.
v5.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.37.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.
v5.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.36.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.
v5.35.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.
v5.34.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.
v5.33.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.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.
v5.31.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.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.
v5.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.30.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.
v5.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.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.
v5.14.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.
v5.13.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.
v5.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.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.