← Home

@material-symbols/font-400

84
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

marella

Keywords

material-symbolsmaterial-iconsmaterial-design-iconsmaterial-designmaterialsymbolsiconsfont

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA Sigstore attestation; stable for this package going forward. ai

Versions (showing 84 of 84)

Version Deps Published
0.45.9 0 / 0
0.45.8 0 / 0
0.45.7 0 / 0
0.45.5 0 / 0
0.45.4 0 / 0
0.45.3 0 / 0
0.45.2 0 / 0
0.45.1 0 / 0
0.45.0 0 / 0
0.44.12 0 / 0
0.44.11 0 / 0
0.44.10 0 / 0
0.44.9 0 / 0
0.44.8 0 / 0
0.44.7 0 / 0
0.44.6 0 / 0
0.44.5 0 / 0
0.44.4 0 / 0
0.44.3 0 / 0
0.44.2 0 / 0
0.44.1 0 / 0
0.44.0 0 / 0
0.43.0 0 / 0
0.42.3 0 / 0
0.40.2 0 / 0
0.40.1 0 / 0
0.40.0 0 / 0
0.39.4 0 / 0
0.39.3 0 / 0
0.39.2 0 / 0
0.39.1 0 / 0
0.39.0 0 / 0
0.38.0 0 / 0
0.37.0 0 / 0
0.36.4 0 / 0
0.36.3 0 / 0
0.36.2 0 / 0
0.36.1 0 / 0
0.36.0 0 / 0
0.35.2 0 / 0
0.35.1 0 / 0
0.35.0 0 / 0
0.34.1 0 / 0
0.34.0 0 / 0
0.33.0 0 / 0
0.32.0 0 / 0
0.31.9 0 / 0
0.31.8 0 / 0
0.31.7 0 / 0
0.31.6 0 / 0
0.31.5 0 / 0
0.31.4 0 / 0
0.31.3 0 / 0
0.31.2 0 / 0
0.31.1 0 / 0
0.31.0 0 / 0
0.30.0 0 / 0
0.29.3 0 / 0
0.29.2 0 / 0
0.29.1 0 / 0
0.29.0 0 / 0
0.28.2 0 / 0
0.28.1 0 / 0
0.28.0 0 / 0
0.27.2 0 / 0
0.27.1 0 / 0
0.27.0 0 / 0
0.26.0 0 / 0
0.25.3 0 / 0
0.25.2 0 / 0
0.25.1 0 / 0
0.25.0 0 / 0
0.24.0 0 / 0
0.23.0 0 / 0
0.22.2 0 / 0
0.22.1 0 / 0
0.22.0 0 / 0
0.21.3 0 / 0
0.21.2 0 / 0
0.21.1 0 / 0
0.21.0 0 / 0
0.20.0 0 / 0
0.19.0 0 / 0
0.18.0 0 / 0

v0.45.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.45.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.45.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.45.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.31.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.

v0.31.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.

v0.31.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.

v0.30.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.

v0.29.3

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.

v0.29.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.

v0.29.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.

v0.29.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.

v0.28.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.

v0.28.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.

v0.28.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.

v0.27.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.

v0.27.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.

v0.27.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.

v0.26.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.

v0.25.3

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.

v0.25.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.

v0.25.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.

v0.25.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.

v0.24.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.

v0.23.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.

v0.22.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.

v0.22.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.

v0.22.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.

v0.21.3

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.

v0.21.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.

v0.21.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.

v0.21.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.

v0.20.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.

v0.19.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.

v0.18.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.