sauce-tunnel
A wrapper around the Sauce Labs tunnel jar
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): sauce-tunnel's core purpose is wrapping the Sauce Labs sc binary; bundled platform binaries (darwin, linux, win32) are expected and documented for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used solely to spawn the bundled Sauce Connect binary — intrinsic to this package's purpose as a binary wrapper. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): spawn() launches the bundled sc binary from a fixed vendor path; this is the documented, expected behavior of this wrapper package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 3 / 0 | |
| 2.4.0 | 3 / 0 | |
| 2.3.0 | 3 / 0 | |
| 2.2.3 | 3 / 0 | |
| 2.2.2 | 3 / 0 | |
| 2.1.1 | 2 / 0 | |
| 2.1.0 | 2 / 0 | |
| 2.0.4 | 2 / 0 | |
| 2.0.3 | 2 / 0 | |
| 2.0.2 | 2 / 0 | |
| 2.0.1 | 2 / 0 | |
| 2.0.0 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.0.2 | 2 / 0 | |
| 1.0.0 | 2 / 0 |
v2.5.0
3 findingsPackage contains compiled binaries that could be backdoors: • vendor/darwin/bin/sc • vendor/darwin/bin/sc.dSYM/Contents/Resources/DWARF/sc • vendor/linux/bin/sc • vendor/linux32/bin/sc • vendor/win32/bin/sc.exe
Maintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsMaintainer email '[email protected]' uses domain 'rzrsharp.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.