@contentful/field-editor-radio
```bash npm install @contentful/field-editor-radio ```
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @emotion/css is the canonical Emotion CSS package; swap from `emotion` is a standard migration, not a supply-chain risk. | ai | |
| provenance | publisher-changed | AI (provenance): Contentful org migrated publishing to GitHub Actions CI; consistent with org-wide CI/CD transition across their packages. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): First-party Contentful design system component; same org as this package, stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Contentful org publishes via GitHub Actions CI; absence of Sigstore attestation is consistent across their packages. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 5 / 3 | |
| 3.1.0 | 5 / 3 | |
| 3.0.5 | 5 / 3 | |
| 3.0.4 | 5 / 3 | |
| 3.0.3 | 5 / 3 | |
| 3.0.2 | 5 / 3 | |
| 3.0.1 | 5 / 3 | |
| 3.0.0 | 5 / 3 | |
| 2.0.7 | 5 / 3 | |
| 2.0.6 | 5 / 3 | |
| 2.0.5 | 5 / 3 | |
| 2.0.4 | 5 / 3 | |
| 2.0.3 | 5 / 3 | |
| 2.0.2 | 5 / 3 | |
| 2.0.1 | 5 / 3 | |
| 2.0.0 | 5 / 3 | |
| 1.8.5 | 5 / 3 | |
| 1.8.4 | 5 / 3 | |
| 1.8.3 | 5 / 3 | |
| 1.8.2 | 5 / 3 | |
| 1.8.1 | 5 / 3 |
v3.1.1
1 finding[Accepted risk] 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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
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.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.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.
v1.8.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.
v1.8.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.