@vscode/vsce
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): vsce legitimately invokes yarn/npm via child_process for dependency resolution; stable pattern for this tool. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env spread passes DISABLE_V* vars to yarn; expected behavior for this build tool. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('import(...)') is a documented CJS-to-ESM interop workaround for @secretlint/node; not arbitrary code execution. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): @vscode/vsce is the official Microsoft VS Code extension manager; not a typosquat of vite. | ai | |
| phantom-deps | phantom-dep:secretlint | AI (phantom-deps): secretlint is used as a CLI tool via child_process, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@secretlint/secretlint-rule-no-dotenv | AI (phantom-deps): Used as a secretlint plugin loaded dynamically, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@secretlint/secretlint-formatter-sarif | AI (phantom-deps): Used as a secretlint formatter loaded dynamically, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@secretlint/secretlint-rule-preset-recommend | AI (phantom-deps): Used as a secretlint plugin loaded dynamically, not directly imported; stable false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.9.2 | 30 / 19 | |
| 3.9.1 | 30 / 20 | |
| 3.9.0 | 30 / 20 | |
| 3.8.1 | 30 / 20 | |
| 3.8.0 | 30 / 20 | |
| 3.7.1 | 30 / 20 | |
| 3.7.0 | 30 / 20 | |
| 3.6.2 | 30 / 20 | |
| 3.6.1 | 30 / 20 | |
| 3.6.0 | 30 / 20 | |
| 3.5.0 | 30 / 20 | |
| 3.4.2 | 30 / 20 | |
| 3.4.1 | 29 / 20 | |
| 3.4.0 | 29 / 20 | |
| 3.3.2 | 24 / 20 | |
| 3.3.1 | 24 / 20 | |
| 3.3.0 | 24 / 20 | |
| 3.2.2 | 24 / 20 | |
| 3.2.1 | 24 / 20 | |
| 3.2.0 | 24 / 20 | |
| 3.1.1 | 24 / 20 | |
| 3.1.0 | 24 / 20 | |
| 3.0.0 | 24 / 20 |
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (vscode-bot) on 2025-01-29, but microsoft1es 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.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.