@contentful/field-editor-number
```bash npm install @contentful/field-editor-number ```
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Contentful monorepo uses automated CI publishing; rapid successive releases are normal for this package family. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @emotion/css is the canonical successor to emotion; this is a routine dependency migration for this Contentful package. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): Contentful's own Forma 36 design system; first-party dependency stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Contentful publishes via GitHub Actions CI; provenance absence is consistent across their package ecosystem. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 5 / 4 | |
| 2.1.0 | 5 / 4 | |
| 2.0.13 | 5 / 4 | |
| 2.0.12 | 5 / 4 | |
| 2.0.11 | 5 / 4 | |
| 2.0.10 | 5 / 4 | |
| 2.0.9 | 5 / 4 | |
| 2.0.8 | 5 / 4 | |
| 2.0.7 | 5 / 4 | |
| 2.0.6 | 5 / 4 | |
| 2.0.5 | 5 / 4 | |
| 2.0.4 | 5 / 4 | |
| 2.0.3 | 5 / 4 | |
| 2.0.2 | 5 / 4 | |
| 2.0.1 | 5 / 4 | |
| 2.0.0 | 5 / 4 | |
| 1.6.5 | 5 / 4 | |
| 1.6.4 | 5 / 4 | |
| 1.6.3 | 5 / 4 | |
| 1.6.2 | 5 / 4 | |
| 1.6.1 | 5 / 4 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.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.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.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.
v1.6.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.