@microsoft/dev-tunnels-connections
Tunnels library for Visual Studio tools
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is a declared transitive/config dependency in this Microsoft SDK package; phantom-dep firing is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is a declared polyfill dependency used in build/config context; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:es5-ext | AI (phantom-deps): es5-ext is a declared dependency used in build/config context; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:await-semaphore | AI (phantom-deps): await-semaphore is a declared dependency used in build/config context; phantom-dep is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@microsoft/dev-tunnels-contracts | AI (dependencies): Sibling package in the same Microsoft dev-tunnels suite, published at the same coordinated version. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@microsoft/dev-tunnels-management | AI (dependencies): Sibling package in the same Microsoft dev-tunnels suite, published at the same coordinated version. Not a third-party risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft SDK package with 65k weekly downloads and 122 versions. Short README and missing repo URL are metadata gaps, not spam/malware indicators. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.3.48 | 9 / 0 | |
| 1.3.46 | 9 / 0 | |
| 1.3.45 | 9 / 0 | |
| 1.3.43 | 9 / 0 | |
| 1.3.41 | 9 / 0 | |
| 1.3.40 | 9 / 0 | |
| 1.3.37 | 9 / 0 | |
| 1.3.36 | 9 / 0 | |
| 1.3.6 | 11 / 0 | |
| 1.3.5 | 11 / 0 | |
| 1.3.4 | 11 / 0 | |
| 1.3.3 | 11 / 0 |
v1.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.