@vscode/test-electron
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Test fixture string, not actual file access; stable false positive. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal org maintainer roster change for Microsoft-owned package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Used to spawn decompressor for downloaded VSCode binaries; core documented function. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Expected: package downloads and launches VS Code electron binaries, requiring child_process by design. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official @vscode scoped Microsoft package; sparse metadata is not indicative of spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Known Microsoft package; missing description is a metadata gap, not a risk signal. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 5 / 11 | |
| 3.0.0 | 5 / 11 | |
| 2.5.2 | 5 / 11 | |
| 2.5.1 | 5 / 11 | |
| 2.4.1 | 5 / 11 | |
| 2.4.0 | 5 / 11 | |
| 2.3.10 | 4 / 12 |
v3.1.0
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 157 | await fs.mkdir(contentsDir, { recursive: true }); 158 | await fs.writeFile(join(contentsDir, 'Info.plist'), '<?xml version="1.0"?><plist version="1.0"><dict>' + > 159 | '<key>CFBundleExecutable</key><string>../../../etc/passwd</string>' + 160 | '</dict></plist>'); 161 | await touchExecutable(bundleName, 'Code');
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
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-04-07, 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.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.