← Home

@contentful/field-editor-location

npm Repository Homepage

```bash npm install @contentful/field-editor-location ```

21
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

it-internalwhydah-gallycontentful-ecosystemmichaelpearce

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Contentful org migrated publishing to GitHub Actions CI; consistent with org-wide automation shift across their packages. ai
dependencies unvetted-dep:@types/google-map-react AI (dependencies): Type definitions for google-map-react; stable dev/type dep for this location field editor package. ai
dependencies unvetted-dep:@contentful/f36-components AI (dependencies): Contentful's own design system component library; expected dependency for all Contentful field editor packages. ai
provenance no-provenance AI (provenance): Contentful publishes via GitHub Actions CI; provenance absence is consistent across their package ecosystem. ai
phantom-deps phantom-dep:@types/google-map-react AI (phantom-deps): Type-only package; not directly imported at runtime by convention — stable false positive for this package. ai

Versions (showing 21 of 21)

Version Deps Published
2.1.1 7 / 2
2.1.0 7 / 2
2.0.13 7 / 2
2.0.12 7 / 2
2.0.11 7 / 2
2.0.10 7 / 2
2.0.9 7 / 2
2.0.8 7 / 2
2.0.7 7 / 2
2.0.6 7 / 2
2.0.5 7 / 2
2.0.4 7 / 2
2.0.3 7 / 2
2.0.2 7 / 2
2.0.1 7 / 2
2.0.0 7 / 2
1.5.25 7 / 2
1.5.24 7 / 2
1.5.23 7 / 2
1.5.22 7 / 2
1.5.21 7 / 2

v2.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.13

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.24

2 findings
HIGH Publisher changed: contentful-ecosystem → GitHub Actions (on 2026-02-23) provenance

This version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.23

2 findings
HIGH Publisher changed: contentful-ecosystem → GitHub Actions (on 2026-01-22) provenance

This version was published by a different npm account than previous versions on 2026-01-22. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.22

2 findings
HIGH Publisher changed: contentful-ecosystem → GitHub Actions (on 2026-01-19) provenance

This version was published by a different npm account than previous versions on 2026-01-19. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.