@contentful/field-editor-rich-text
```bash npm install @contentful/field-editor-rich-text ```
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 | publisher-changed | AI (provenance): Contentful org uses GitHub Actions for automated publishing; this transition is consistent across their package ecosystem. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): slate-dom is part of the slate ecosystem already used by this package; version-aligned addition, not suspicious. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): Official Contentful Forma 36 component library; stable for this package. | ai | |
| dependencies | unvetted-dep:@udecode/plate-list | AI (dependencies): Well-known @udecode/plate editor library; stable for this package. | ai | |
| dependencies | unvetted-dep:@udecode/plate-serializer-docx | AI (dependencies): Well-known @udecode/plate editor library; stable for this package. | ai | |
| dependencies | unvetted-dep:@udecode/plate-table | AI (dependencies): Well-known @udecode/plate editor library; stable for this package. | ai | |
| dependencies | unvetted-dep:@contentful/app-sdk | AI (dependencies): Official Contentful SDK; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI for an established Contentful org package; provenance gap is low risk here. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Used transitively via react-popper; phantom-dep heuristic fires but it's a legitimate declared dep. | ai | |
| phantom-deps | phantom-dep:@udecode/plate-core | AI (phantom-deps): Declared as direct dep for types/config; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 6.3.9 | 37 / 7 | |
| 6.3.8 | 37 / 7 | |
| 6.3.7 | 37 / 7 | |
| 6.3.6 | 37 / 7 | |
| 6.3.5 | 37 / 7 | |
| 6.3.4 | 37 / 7 | |
| 6.3.3 | 37 / 7 | |
| 6.3.2 | 37 / 7 | |
| 6.3.1 | 37 / 7 | |
| 6.3.0 | 37 / 7 | |
| 6.2.1 | 37 / 7 | |
| 6.2.0 | 37 / 7 | |
| 6.1.1 | 37 / 7 | |
| 6.1.0 | 37 / 7 | |
| 6.0.0 | 37 / 7 | |
| 5.0.9 | 37 / 7 | |
| 5.0.8 | 37 / 7 | |
| 5.0.7 | 37 / 7 | |
| 5.0.6 | 37 / 7 | |
| 5.0.5 | 37 / 7 | |
| 5.0.4 | 37 / 7 | |
| 5.0.3 | 37 / 7 | |
| 5.0.2 | 37 / 7 | |
| 5.0.1 | 37 / 7 | |
| 5.0.0 | 37 / 7 | |
| 4.20.14 | 35 / 7 | |
| 4.20.13 | 35 / 7 | |
| 4.20.12 | 35 / 7 | |
| 4.20.11 | 35 / 7 | |
| 4.20.10 | 35 / 7 | |
| 4.20.9 | 35 / 7 | |
| 4.20.8 | 35 / 7 | |
| 4.20.7 | 35 / 7 | |
| 4.20.6 | 35 / 7 | |
| 4.20.5 | 35 / 7 | |
| 4.20.4 | 35 / 7 | |
| 4.20.3 | 35 / 7 | |
| 4.20.2 | 35 / 7 | |
| 4.20.1 | 35 / 7 | |
| 4.20.0 | 35 / 7 | |
| 4.19.4 | 35 / 7 | |
| 4.19.3 | 35 / 7 | |
| 4.19.2 | 35 / 7 | |
| 4.19.1 | 35 / 7 | |
| 4.19.0 | 35 / 7 | |
| 4.18.0 | 34 / 7 | |
| 4.17.9 | 34 / 7 | |
| 4.17.8 | 34 / 7 | |
| 4.17.7 | 35 / 7 | |
| 4.17.6 | 35 / 7 | |
| 4.17.5 | 35 / 7 |
v6.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.8
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.20.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.6
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.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.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.
v4.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.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.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.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.
v4.19.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-29. 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.
v4.19.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. 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.
v4.18.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-15. 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.
v4.17.9
2 findingsThis version was published by a different npm account than previous versions on 2025-12-08. 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.
v4.17.8
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.17.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (contentful-ecosystem) than the most recent previously approved version (GitHub Actions) on 2025-12-02, but contentful-ecosystem is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.