@contentful/field-editor-validation-errors
```bash npm install @contentful/field-editor-validation-errors ```
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 official successor to emotion; this is a standard library migration, not a suspicious new dep. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): @contentful/f36-components is Contentful's own design system; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions from official Contentful org repo; provenance gap is common and not a risk signal here. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 5 / 2 | |
| 3.1.0 | 5 / 2 | |
| 3.0.13 | 5 / 2 | |
| 3.0.12 | 5 / 2 | |
| 3.0.11 | 5 / 2 | |
| 3.0.10 | 5 / 2 | |
| 3.0.9 | 5 / 2 | |
| 3.0.8 | 5 / 2 | |
| 3.0.7 | 5 / 2 | |
| 3.0.6 | 5 / 2 | |
| 3.0.5 | 5 / 2 | |
| 3.0.4 | 5 / 2 | |
| 3.0.3 | 5 / 2 | |
| 3.0.2 | 5 / 2 | |
| 3.0.1 | 5 / 2 | |
| 3.0.0 | 5 / 2 | |
| 2.1.2 | 5 / 2 | |
| 2.1.1 | 5 / 2 | |
| 2.1.0 | 5 / 2 | |
| 2.0.7 | 5 / 2 |
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.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
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.3
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.1
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.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.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.
v2.0.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.