@vscode/proxy-agent
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
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): Expected in a proxy agent that interacts with system cert stores; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@vscode/windows-ca-certs | AI (dependencies): Optional dep from the same Microsoft @vscode namespace; legitimate Windows CA cert integration. | ai | |
| phantom-deps | phantom-dep:@tootallnate/once | AI (phantom-deps): Declared as a runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.44.0 | 8 / 6 | |
| 0.43.0 | 8 / 6 | |
| 0.42.0 | 8 / 6 | |
| 0.41.0 | 8 / 6 | |
| 0.40.0 | 8 / 6 | |
| 0.39.1 | 8 / 6 | |
| 0.39.0 | 8 / 6 | |
| 0.38.0 | 8 / 6 | |
| 0.37.0 | 8 / 3 | |
| 0.36.0 | 8 / 3 | |
| 0.35.0 | 8 / 3 | |
| 0.34.0 | 8 / 3 | |
| 0.33.0 | 8 / 3 | |
| 0.32.0 | 7 / 3 | |
| 0.31.0 | 7 / 3 | |
| 0.30.0 | 7 / 3 | |
| 0.29.0 | 7 / 3 | |
| 0.28.0 | 7 / 3 | |
| 0.27.0 | 7 / 3 | |
| 0.26.0 | 7 / 3 | |
| 0.25.0 | 6 / 3 | |
| 0.24.0 | 6 / 3 | |
| 0.23.0 | 6 / 3 | |
| 0.22.0 | 6 / 3 | |
| 0.21.0 | 6 / 3 | |
| 0.20.0 | 6 / 3 |
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
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 2024-11-19, 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.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.