← Home

@contentful/f36-icons

npm Repository Homepage
22
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

it-internalwhydah-gallycontentful-ecosystemmichaelpearce

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@contentful/f36-core AI (dependencies): Same-org monorepo sibling; stable dependency pattern for this package. ai
dependencies unvetted-dep:@contentful/f36-icon AI (dependencies): Same-org monorepo sibling; stable dependency pattern for this package. ai
dependencies unvetted-dep:@contentful/f36-tokens AI (dependencies): Same-org monorepo sibling; stable dependency pattern for this package. ai
phantom-deps phantom-dep:@contentful/f36-core AI (phantom-deps): Same-org monorepo dep; may be re-exported or used indirectly via build tooling. ai
phantom-deps phantom-dep:@contentful/f36-tokens AI (phantom-deps): Same-org monorepo dep; may be re-exported or used indirectly via build tooling. ai
phantom-deps phantom-dep:@emotion/css AI (phantom-deps): CSS-in-JS dep likely used in build scripts or config; stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Established design system component; sparse README is a style choice, not a spam indicator. ai

Versions (showing 22 of 22)

Version Deps Published
6.9.1 5 / 2
6.9.0 5 / 2
6.8.0 5 / 2
6.7.4 5 / 2
6.7.3 5 / 2
6.7.2 5 / 2
6.7.1 5 / 2
6.7.0 5 / 2
6.6.1 5 / 2
6.6.0 5 / 2
6.5.1 5 / 2
6.5.0 5 / 2
6.3.2 5 / 2
6.3.1 5 / 2
6.2.0 5 / 2
6.1.0 5 / 2
6.0.0 5 / 2
5.9.1 5 / 2
5.9.0 5 / 2
5.8.1 5 / 2
5.8.0 5 / 2
5.7.0 5 / 2

v6.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.7.2

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.

v6.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.9.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.

v5.8.1

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.

v5.8.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.

v5.7.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.