@contentful/f36-autocomplete
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@contentful/f36-core | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released at the same version. | ai | |
| dependencies | unvetted-dep:@contentful/f36-forms | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released at the same version. | ai | |
| dependencies | unvetted-dep:@contentful/f36-icons | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released at the same version. | ai | |
| dependencies | unvetted-dep:@contentful/f36-utils | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released together. | ai | |
| dependencies | unvetted-dep:@contentful/f36-button | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released at the same version. | ai | |
| dependencies | unvetted-dep:@contentful/f36-popover | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released at the same version. | ai | |
| dependencies | unvetted-dep:@contentful/f36-skeleton | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released at the same version. | ai | |
| dependencies | unvetted-dep:@contentful/f36-typography | AI (dependencies): Sibling package in the Contentful Forma 36 monorepo; co-released at the same version. | ai | |
| provenance | no-provenance | AI (provenance): Established Contentful org package; absence of Sigstore provenance is not a risk signal here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 6.9.1 | 11 / 0 | |
| 6.9.0 | 11 / 0 | |
| 6.8.0 | 11 / 0 | |
| 6.7.4 | 11 / 0 | |
| 6.7.3 | 11 / 0 | |
| 6.7.2 | 11 / 0 | |
| 6.7.1 | 11 / 0 | |
| 6.7.0 | 11 / 0 | |
| 6.6.1 | 11 / 0 | |
| 6.6.0 | 11 / 0 | |
| 6.5.1 | 11 / 0 | |
| 6.5.0 | 11 / 0 | |
| 6.3.2 | 11 / 0 | |
| 6.3.1 | 11 / 0 | |
| 6.2.0 | 11 / 0 | |
| 6.1.0 | 11 / 0 | |
| 6.0.0 | 11 / 0 | |
| 5.9.1 | 11 / 0 | |
| 5.9.0 | 11 / 0 | |
| 5.8.1 | 11 / 0 | |
| 5.8.0 | 11 / 0 | |
| 5.7.0 | 11 / 0 |
v6.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.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.
v6.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.