@microsoft/dev-tunnels-contracts MIT 51 versions

@microsoft/dev-tunnels-contracts

npm

Tunnels library for Visual Studio tools

51

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

microsoft1esmicrosoft-oss-releasesdebekoe-msftdevtunnels

Keywords

Tunnels

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:vscode-jsonrpc	AI (phantom-deps): Likely used indirectly in build output; long-standing Microsoft package.	ai	2026/07/20
phantom-deps	phantom-dep:debug	AI (phantom-deps): Common utility dep, referenced in config; false positive pattern.	ai	2026/07/20
phantom-deps	phantom-dep:buffer	AI (phantom-deps): Common polyfill dep; false positive pattern.	ai	2026/07/20

Versions (showing 51 of 124)

View all versions

Version	Deps	Published
1.3.50	3 / 0	2026-06-22
1.3.49	3 / 0	2026-06-19
1.3.48	3 / 0	2026-05-06
1.3.46	3 / 0	2026-05-02
1.3.45	3 / 0	2026-04-25
1.3.43	3 / 0	2026-04-22
1.3.41	3 / 0	2026-04-03
1.3.40	3 / 0	2026-04-03
1.3.37	3 / 0	2026-04-03
1.3.36	3 / 0	2026-04-02
1.3.6	3 / 0	2025-08-22
1.3.5	3 / 0	2025-08-20
1.3.4	3 / 0	2025-08-19
1.3.3	3 / 0	2025-08-12
1.2.1	3 / 0	2024-09-27
1.1.47	3 / 0	2024-09-27
1.1.45	3 / 0	2024-08-22
1.1.36	3 / 0	2024-05-02
1.1.33	3 / 0	2024-03-29
1.1.32	3 / 0	2024-03-19
1.1.26	3 / 0	2024-03-05
1.1.24	3 / 0	2024-02-23
1.1.23	3 / 0	2024-02-15
1.1.22	3 / 0	2024-02-15
1.1.16	3 / 0	2024-01-31
1.1.11	3 / 0	2024-01-29
1.1.10	3 / 0	2024-01-25
1.1.9	3 / 0	2024-01-24
1.1.8	3 / 0	2024-01-23
1.1.6	3 / 0	2024-01-09
1.1.5	3 / 0	2024-01-04
1.1.4	3 / 0	2024-01-04
1.1.1	3 / 0	2023-12-19
1.0.7474	3 / 0	2023-12-18
1.0.7473	3 / 0	2023-12-18
1.0.7471	3 / 0	2023-12-15
1.0.7470	3 / 0	2023-12-12
1.0.7469	3 / 0	2023-12-11
1.0.7466	3 / 0	2023-12-06
1.0.7463	3 / 0	2023-11-29
1.0.7462	3 / 0	2023-11-27
1.0.7459	3 / 0	2023-11-02
1.0.7458	3 / 0	2023-10-31
1.0.7456	3 / 0	2023-10-31
1.0.7452	3 / 0	2023-10-27
1.0.7451	3 / 0	2023-10-27
1.0.7445	3 / 0	2023-10-18
1.0.7442	3 / 0	2023-10-12
1.0.7440	3 / 0	2023-10-11
1.0.7438	3 / 0	2023-10-05
1.0.7437	3 / 0	2023-10-04

v1.3.41

1 finding

LOW No provenance attestation provenance

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

v1.2.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.

v1.1.47

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.

v1.1.45

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.

v1.1.36

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.

v1.1.33

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.

v1.1.32

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.

v1.1.26

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.

v1.1.24

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.

v1.1.23

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.

v1.1.22

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.

v1.1.16

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.

v1.1.11

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.

v1.1.10

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.

v1.1.9

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.

v1.1.8

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.

v1.1.6

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.

v1.1.5

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.

v1.1.4

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.

v1.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.

v1.0.7474

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.

v1.0.7473

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.

v1.0.7471

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.

v1.0.7470

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.

v1.0.7469

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.

v1.0.7466

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.

v1.0.7463

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.

v1.0.7462

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.

v1.0.7459

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.

v1.0.7458

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.

v1.0.7456

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.

v1.0.7452

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.

v1.0.7451

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.

v1.0.7445

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.

v1.0.7442

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.

v1.0.7440

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.

v1.0.7438

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.

v1.0.7437

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.