@contentful/field-editor-shared
This package contains shared code (components, utilities, test utilities) that is used by all other field editor packages.
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:@contentful/f36-note | AI (dependencies): First-party Contentful design system dep; 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 of this package. | ai | |
| provenance | no-provenance | AI (provenance): Official Contentful org package published via GitHub Actions; provenance gap is cosmetic for this publisher. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 8 / 5 | |
| 4.4.0 | 8 / 5 | |
| 4.3.0 | 8 / 5 | |
| 4.2.0 | 8 / 5 | |
| 4.1.2 | 8 / 5 | |
| 4.1.1 | 8 / 5 | |
| 4.1.0 | 8 / 5 | |
| 4.0.0 | 8 / 5 | |
| 3.1.4 | 8 / 5 | |
| 3.1.3 | 8 / 5 | |
| 3.1.2 | 8 / 5 | |
| 3.1.1 | 8 / 5 | |
| 3.1.0 | 8 / 5 | |
| 3.0.2 | 8 / 5 | |
| 3.0.1 | 8 / 5 | |
| 3.0.0 | 8 / 5 | |
| 2.18.1 | 8 / 5 | |
| 2.18.0 | 8 / 5 | |
| 2.17.1 | 8 / 5 | |
| 2.17.0 | 8 / 4 |
v4.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
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.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.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.
v2.17.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.