← Home

vscode-nls

NPM module to externalize and localize VSCode extensions

29
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jriekenegammachrisdiasalexandrudimaaeschlidbaeumerbpaseroisidorjoaomoreno.mstylerl0706

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition within Microsoft's VS Code team; tylerl0706 (Tyler Leonhardt) is a known Microsoft employee. ai
maintainer-change maintainer-added AI (maintainer-change): tylerl0706 is a known Microsoft VS Code team member with strong track record (73 approvals, 0 rejections). ai

Versions (showing 29 of 29)

Version Deps Published
5.2.0 0 / 7
5.1.0 0 / 7
5.0.1 0 / 7
5.0.0 0 / 7
4.1.2 0 / 7
4.1.1 0 / 4
4.1.0 0 / 4
4.0.0 0 / 4
3.2.5 0 / 4
3.2.4 0 / 4
3.2.3 0 / 4
3.2.2 0 / 4
3.2.1 0 / 4
3.2.0 0 / 4
3.1.2 0 / 4
3.1.1 0 / 4
3.1.0 0 / 4
3.0.0 0 / 4
2.0.2 0 / 4
2.0.1 0 / 2
2.0.0 0 / 2
1.0.7 0 / 2
1.0.6 0 / 2
1.0.5 0 / 2
1.0.4 0 / 2
1.0.3 0 / 2
1.0.2 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2

v5.2.0

1 finding
LOW No provenance attestation provenance

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

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.1

2 findings
HIGH Publisher changed: dbaeumer → tylerl0706 (on 2022-04-26) provenance

This version was published by a different npm account than previous versions on 2022-04-26. 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.

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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