← Home

@vscode/common-python-lsp

npm Repository Homepage

Shared TypeScript utilities for VS Code Python tool extensions

9
Versions
MIT
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

vscode-botmicrosoft1es

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:@vscode/python-environments AI (npm-metadata): URL points to Microsoft-controlled Azure DevOps feed; expected pattern for internal @vscode packages. ai
bogus-package bogus-package AI (bogus-package): Legitimate Microsoft utility library; sparse README/keywords are common for internal tooling packages. ai

Versions (showing 9 of 9)

Version Deps Published
0.5.2 6 / 15
0.5.1 6 / 15
0.5.0 6 / 15
0.4.0 6 / 15
0.3.0 6 / 15
0.2.1 6 / 15
0.2.0 6 / 15
0.1.1 6 / 15
0.1.0 6 / 15

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

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