@contentful/field-editor-date
```bash npm install @contentful/field-editor-date ```
29
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
it-internalwhydah-gallycontentful-ecosystemmichaelpearce
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @emotion/css is a direct, well-known replacement for the removed `emotion` dep; no supply-chain risk. | ai | |
| provenance | publisher-changed | AI (provenance): Contentful org migrated publishing to GitHub Actions CI/CD; consistent with org-wide automation pattern across their packages. | ai | |
| dependencies | unvetted-dep:@contentful/f36-components | AI (dependencies): First-party Contentful design system dependency; stable false positive for 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 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 5 / 5 | |
| 2.2.0 | 5 / 5 | |
| 2.1.1 | 5 / 5 | |
| 2.1.0 | 5 / 5 | |
| 2.0.19 | 5 / 5 | |
| 2.0.18 | 5 / 5 | |
| 2.0.17 | 5 / 5 | |
| 2.0.16 | 5 / 5 | |
| 2.0.15 | 5 / 5 | |
| 2.0.14 | 5 / 5 | |
| 2.0.13 | 5 / 5 | |
| 2.0.12 | 5 / 5 | |
| 2.0.11 | 5 / 5 | |
| 2.0.10 | 5 / 5 | |
| 2.0.9 | 5 / 5 | |
| 2.0.8 | 5 / 5 | |
| 2.0.7 | 5 / 5 | |
| 2.0.6 | 5 / 5 | |
| 2.0.5 | 5 / 5 | |
| 2.0.4 | 5 / 5 | |
| 2.0.3 | 5 / 5 | |
| 2.0.2 | 5 / 5 | |
| 2.0.1 | 5 / 5 | |
| 2.0.0 | 5 / 5 | |
| 1.9.25 | 5 / 5 | |
| 1.9.24 | 5 / 5 | |
| 1.9.23 | 5 / 5 | |
| 1.9.22 | 5 / 5 | |
| 1.9.21 | 5 / 5 |
v2.2.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.2.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.