@contentful/contentful-slatejs-adapter
15
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo CI publish metadata gap, no behavioral change in diff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived low-churn package; dormancy consistent with maintenance cadence. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 16.2.2 | 1 / 10 | |
| 16.2.1 | 1 / 10 | |
| 16.2.0 | 1 / 10 | |
| 16.1.6 | 1 / 10 | |
| 16.1.5 | 1 / 10 | |
| 16.1.4 | 1 / 10 | |
| 16.1.3 | 1 / 10 | |
| 16.1.2 | 1 / 10 | |
| 16.1.1 | 1 / 10 | |
| 16.1.0 | 1 / 10 | |
| 16.0.4 | 1 / 10 | |
| 16.0.3 | 1 / 10 | |
| 16.0.2 | 1 / 10 | |
| 16.0.1 | 1 / 10 | |
| 16.0.0 | 1 / 10 |
v16.2.2
2 findings
HIGH
Missing gitHead — previous versions had it
provenance
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.