← Home

@vscode/codicons

npm Repository Homepage

The icon font for Visual Studio Code

22
Versions
CC-BY-4.0
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

kaimaetzellszomorualexandrudimasbattenjoaomoreno.msmicrosoft1esrebornixvscode-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Microsoft consolidating to service accounts; legitimate org handoff. ai
provenance publisher-changed-stale AI (provenance): microsoft1es is Microsoft's publishing account; 250d unremoved rules out takeover. ai
semgrep semgrep:child-process-import AI (semgrep): Local git version-bump script; no fetched/hostile target. ai
install-scripts install-script:preinstall AI (install-scripts): preinstall runs npm-force-resolutions to enforce declared resolutions; benign and stable for this package. ai

Versions (showing 22 of 22)

Version Deps Published
0.0.45 0 / 6
0.0.43 0 / 6
0.0.42 0 / 6
0.0.36 0 / 6
0.0.35 0 / 6
0.0.34 0 / 6
0.0.33 0 / 6
0.0.32 0 / 6
0.0.31 0 / 6
0.0.30 0 / 6
0.0.29 0 / 6
0.0.28 0 / 6
0.0.27 0 / 6
0.0.26 0 / 6
0.0.25 0 / 5
0.0.24 0 / 6
0.0.23 0 / 5
0.0.22 0 / 5
0.0.21 0 / 5
0.0.20 0 / 4
0.0.19 0 / 4
0.0.18 0 / 4

v0.0.45

3 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: microsoft1es.

HIGH Publisher changed: mistople → microsoft1es (on 2026-03-12) provenance

This version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.43

3 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: microsoft1es.

MEDIUM Publisher changed: mistople → microsoft1es (on 2025-11-20, unremoved on npm for 241d) provenance

This version was published by a different npm account (microsoft1es) than the most recent previously approved version (mistople) on 2025-11-20. It has since remained available on npm for 241 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.0.42

3 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: microsoft1es.

MEDIUM Publisher changed: mistople → microsoft1es (on 2025-11-11, unremoved on npm for 250d) provenance

This version was published by a different npm account (microsoft1es) than the most recent previously approved version (mistople) on 2025-11-11. It has since remained available on npm for 250 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.0.34

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: miguelsolorio → mistople (on 2023-10-27, known maintainer) provenance

This version was published by a different npm account (mistople) than the most recent previously approved version (miguelsolorio) on 2023-10-27, but mistople is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.33

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: miguelsolorio → mistople (on 2023-05-01, known maintainer) provenance

This version was published by a different npm account (mistople) than the most recent previously approved version (miguelsolorio) on 2023-05-01, but mistople is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.32

1 finding
LOW No provenance attestation provenance

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

v0.0.31

1 finding
LOW No provenance attestation provenance

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

v0.0.30

1 finding
LOW No provenance attestation provenance

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

v0.0.29

1 finding
LOW No provenance attestation provenance

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

v0.0.28

1 finding
LOW No provenance attestation provenance

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

v0.0.27

1 finding
LOW No provenance attestation provenance

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

v0.0.26

1 finding
LOW No provenance attestation provenance

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

v0.0.25

1 finding
LOW No provenance attestation provenance

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

v0.0.24

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npx npm-force-resolutions

LOW No provenance attestation provenance

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

v0.0.23

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: npx npm-force-resolutions

LOW No provenance attestation provenance

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

v0.0.22

1 finding
LOW No provenance attestation provenance

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

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

1 finding
LOW No provenance attestation provenance

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

v0.0.19

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

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.