@contentful/default-field-editors
```bash npm install @contentful/default-field-editors ```
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Published via GitHub Actions; no provenance attestation is consistent across this package's history. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @emotion/css is the official successor to emotion; this is a standard migration, not a suspicious addition. | ai | |
| provenance | publisher-changed | AI (provenance): contentful-ecosystem is the Contentful org account with 270 approved packages; transition from GH Actions is a legitimate CI publisher change. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): Same Contentful org scope; stable dependency across many versions of this package. | ai | |
| phantom-deps | phantom-dep:@contentful/f36-icons | AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 4.1.4 | 25 / 1 | |
| 4.1.3 | 25 / 1 | |
| 4.1.2 | 25 / 1 | |
| 4.1.1 | 25 / 1 | |
| 4.1.0 | 25 / 1 | |
| 4.0.15 | 25 / 1 | |
| 4.0.14 | 25 / 1 | |
| 4.0.13 | 25 / 1 | |
| 4.0.12 | 25 / 1 | |
| 4.0.10 | 25 / 1 | |
| 4.0.9 | 25 / 1 | |
| 4.0.8 | 25 / 1 | |
| 4.0.7 | 25 / 1 | |
| 4.0.6 | 25 / 1 | |
| 4.0.5 | 25 / 1 | |
| 4.0.4 | 25 / 1 | |
| 4.0.3 | 25 / 1 | |
| 4.0.2 | 25 / 1 | |
| 4.0.1 | 25 / 1 | |
| 4.0.0 | 25 / 1 | |
| 3.0.14 | 25 / 1 | |
| 3.0.13 | 25 / 1 | |
| 3.0.12 | 25 / 1 | |
| 3.0.11 | 25 / 1 | |
| 3.0.10 | 25 / 1 | |
| 3.0.9 | 25 / 1 | |
| 3.0.8 | 25 / 1 | |
| 3.0.7 | 25 / 1 | |
| 3.0.6 | 25 / 1 | |
| 3.0.5 | 25 / 1 | |
| 3.0.4 | 25 / 1 | |
| 3.0.3 | 25 / 1 | |
| 3.0.2 | 25 / 1 | |
| 3.0.1 | 25 / 1 | |
| 3.0.0 | 25 / 1 | |
| 2.2.19 | 25 / 1 | |
| 2.2.18 | 25 / 1 | |
| 2.2.17 | 25 / 1 | |
| 2.2.16 | 25 / 1 | |
| 2.2.15 | 25 / 1 | |
| 2.2.14 | 25 / 1 | |
| 2.2.13 | 25 / 1 | |
| 2.2.12 | 25 / 1 | |
| 2.2.11 | 25 / 1 | |
| 2.2.10 | 25 / 1 | |
| 2.2.9 | 25 / 1 | |
| 2.2.8 | 25 / 1 | |
| 2.2.7 | 25 / 1 | |
| 2.2.6 | 25 / 1 | |
| 2.2.5 | 25 / 1 | |
| 2.2.4 | 25 / 1 |
v4.1.4
1 finding[Accepted risk] Package 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.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
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.6
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.2
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.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage 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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.