@contentful/field-editor-json
```bash npm install @contentful/field-editor-json ```
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/react-codemirror | AI (dependencies): Type-only dependency for codemirror; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): First-party Contentful design system dep; stable for this package family. | ai | |
| phantom-deps | phantom-dep:@types/react-codemirror | AI (phantom-deps): Type-only package; not directly imported at runtime by convention. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Contentful publishes via GitHub Actions CI; provenance absence is consistent across their package family. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 11 / 2 | |
| 4.2.0 | 11 / 2 | |
| 4.1.5 | 11 / 2 | |
| 4.1.4 | 11 / 2 | |
| 4.1.3 | 11 / 2 | |
| 4.1.2 | 11 / 2 | |
| 4.1.1 | 11 / 2 | |
| 4.1.0 | 11 / 2 | |
| 4.0.8 | 10 / 2 | |
| 4.0.7 | 10 / 2 | |
| 4.0.6 | 10 / 2 | |
| 4.0.5 | 10 / 2 | |
| 4.0.4 | 10 / 2 | |
| 4.0.3 | 10 / 2 | |
| 4.0.2 | 10 / 2 | |
| 4.0.1 | 10 / 2 | |
| 4.0.0 | 10 / 2 | |
| 3.6.5 | 10 / 2 | |
| 3.6.4 | 10 / 2 | |
| 3.6.3 | 10 / 2 | |
| 3.6.2 | 10 / 2 | |
| 3.6.1 | 10 / 2 |
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.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.