@rushstack/playwright-browser-tunnel
Run a remote Playwright Browser Tunnel. Useful in remote development environments.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require constructs a path to load a versioned playwright-core peer dep at runtime — a documented, intentional pattern for this package. Not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:playwright | AI (phantom-deps): playwright is declared as a runtime dependency in package.json; phantom-dep is a false positive from incomplete static import tracing. | ai | |
| phantom-deps | phantom-dep:string-argv | AI (phantom-deps): string-argv is declared as a runtime dependency in package.json; phantom-dep is a false positive. | ai | |
| phantom-deps | phantom-dep:@rushstack/ts-command-line | AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep is a false positive from static analysis not tracing all import paths. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.3.20 | 6 / 8 | |
| 0.3.19 | 6 / 8 | |
| 0.3.18 | 6 / 8 | |
| 0.3.17 | 6 / 8 | |
| 0.3.16 | 6 / 8 | |
| 0.3.15 | 6 / 8 | |
| 0.3.14 | 6 / 8 | |
| 0.3.13 | 6 / 8 | |
| 0.3.12 | 6 / 8 | |
| 0.3.11 | 6 / 8 | |
| 0.3.10 | 6 / 8 | |
| 0.3.9 | 6 / 8 | |
| 0.3.8 | 6 / 8 | |
| 0.3.7 | 6 / 8 | |
| 0.3.6 | 6 / 8 | |
| 0.3.5 | 7 / 8 | |
| 0.3.4 | 7 / 8 | |
| 0.3.3 | 7 / 8 | |
| 0.3.2 | 7 / 8 | |
| 0.3.1 | 7 / 8 | |
| 0.3.0 | 7 / 8 | |
| 0.2.4 | 7 / 8 | |
| 0.2.3 | 7 / 8 | |
| 0.2.2 | 7 / 8 | |
| 0.2.1 | 7 / 8 | |
| 0.2.0 | 7 / 8 | |
| 0.1.1 | 7 / 8 | |
| 0.1.0 | 7 / 8 |
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.