← Home

@iconify/tools

4
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

cyberalien

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): Git download utilities legitimately use child_process to run git commands; stable pattern for this package. ai
semgrep semgrep:child-process-exec AI (semgrep): exec() used in misc/exec.cjs as a shell wrapper for git operations; expected for this tool. ai
dependencies unvetted-dep:svgo AI (dependencies): svgo is a well-known SVG optimizer; expected dependency for this SVG tools package. ai
dependencies unvetted-dep:@cyberalien/svg-utils AI (dependencies): Same author's utility package; expected companion dep for this Iconify tooling package. ai
provenance no-provenance AI (provenance): Established package with long history; lack of provenance is consistent across versions. ai

Versions (showing 4 of 4)

Version Deps Published
5.0.12 7 / 16
5.0.11 7 / 16
5.0.1 7 / 16
4.1.5 10 / 14

v5.0.12

1 finding
INFO No provenance attestation provenance

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

v5.0.11

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

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.