@contentful/field-editor-reference
```bash npm i @contentful/field-editor-reference ```
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tanstack/react-query | AI (phantom-deps): @tanstack/react-query is declared in dependencies and actively used; phantom-dep heuristic is a false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): contentful-ecosystem is the Contentful org account with 270 approved packages; transition from GitHub Actions is a legitimate CI change. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): date-fns is a well-established library replacing moment; not a suspicious new dep. | ai | |
| dependencies | unvetted-peer-dep:@contentful/app-sdk | AI (dependencies): Stable Contentful peer dependency; already accepted in prior versions. | ai | |
| dependencies | unvetted-dep:@contentful/field-editor-shared | AI (dependencies): First-party Contentful monorepo sibling dep; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@contentful/mimetype | AI (dependencies): First-party Contentful dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): First-party Contentful design system dep; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@contentful/f36-icons | AI (dependencies): First-party Contentful design system dep; stable pattern across all versions. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 8.3.2 | 17 / 5 | |
| 8.3.1 | 17 / 5 | |
| 8.3.0 | 17 / 5 | |
| 8.2.4 | 17 / 5 | |
| 8.2.3 | 17 / 5 | |
| 8.2.1 | 17 / 5 | |
| 8.2.0 | 17 / 5 | |
| 8.1.1 | 17 / 5 | |
| 8.1.0 | 17 / 5 | |
| 8.0.0 | 17 / 5 | |
| 7.0.10 | 17 / 5 | |
| 7.0.9 | 17 / 5 | |
| 7.0.8 | 17 / 5 | |
| 7.0.7 | 17 / 5 | |
| 7.0.6 | 17 / 5 | |
| 7.0.5 | 17 / 5 | |
| 7.0.4 | 17 / 5 | |
| 7.0.3 | 17 / 5 | |
| 7.0.2 | 17 / 5 | |
| 7.0.1 | 17 / 5 | |
| 7.0.0 | 17 / 5 | |
| 6.22.3 | 17 / 4 | |
| 6.22.2 | 17 / 4 | |
| 6.22.1 | 17 / 4 | |
| 6.22.0 | 17 / 4 | |
| 6.21.2 | 17 / 4 | |
| 6.21.1 | 17 / 4 | |
| 6.21.0 | 17 / 4 | |
| 6.20.1 | 17 / 4 | |
| 6.20.0 | 17 / 4 | |
| 6.19.3 | 17 / 4 | |
| 6.19.2 | 17 / 4 | |
| 6.19.1 | 17 / 4 | |
| 6.19.0 | 17 / 4 | |
| 6.18.0 | 17 / 4 | |
| 6.17.0 | 17 / 4 | |
| 6.16.2 | 17 / 4 | |
| 6.16.1 | 17 / 4 | |
| 6.16.0 | 17 / 4 | |
| 6.15.1 | 17 / 4 |
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.