@contentful/field-editor-tags
```bash npm install @contentful/field-editor-tags ```
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 migrated publishing to GitHub Actions CI; consistent with org-wide automation pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @emotion/css is a well-established Emotion library; swap from `emotion` is a documented migration path, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): First-party Contentful design system package; same org scope, stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Contentful org package published via GitHub Actions; provenance gap is a process issue, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:@contentful/f36-icons | AI (phantom-deps): Same-org Contentful package; phantom-dep heuristic fires on transitive/re-exported usage, stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 10 / 2 | |
| 2.1.0 | 10 / 2 | |
| 2.0.13 | 10 / 2 | |
| 2.0.12 | 10 / 2 | |
| 2.0.11 | 10 / 2 | |
| 2.0.10 | 10 / 2 | |
| 2.0.9 | 10 / 2 | |
| 2.0.8 | 10 / 2 | |
| 2.0.7 | 10 / 2 | |
| 2.0.6 | 10 / 2 | |
| 2.0.5 | 10 / 2 | |
| 2.0.4 | 10 / 2 | |
| 2.0.3 | 10 / 2 | |
| 2.0.2 | 10 / 2 | |
| 2.0.1 | 10 / 2 | |
| 2.0.0 | 10 / 2 | |
| 1.8.5 | 10 / 2 | |
| 1.8.4 | 10 / 2 | |
| 1.8.3 | 10 / 2 | |
| 1.8.2 | 10 / 2 | |
| 1.8.1 | 10 / 2 |
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.
v2.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. 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.
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. 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.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. 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.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. 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.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. 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.
v1.8.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. 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.
v1.8.4
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.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.