@forge/tunnel
Tunnel functionality for Forge CLI
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:child-process-import | AI (semgrep): Used in node-sandbox.js for legitimate sandboxed execution; expected for a tunnel/sandbox package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-supplied handler by filename/name from CLI args; core tunnel functionality, not malicious. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes compressed metrics data via zlib; benign data processing pattern. | ai | |
| phantom-deps | phantom-dep:tmp | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:docker-compose | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 6.4.0 | 18 / 10 | |
| 6.3.17 | 18 / 10 | |
| 6.3.16 | 19 / 11 | |
| 6.3.15 | 19 / 11 | |
| 6.3.14 | 19 / 11 | |
| 6.3.13 | 19 / 11 | |
| 6.3.12 | 19 / 11 | |
| 6.3.11 | 19 / 11 | |
| 6.3.10 | 19 / 11 | |
| 6.3.9 | 19 / 11 | |
| 6.3.8 | 19 / 11 | |
| 6.3.7 | 19 / 11 | |
| 6.3.6 | 19 / 11 | |
| 6.3.5 | 19 / 11 | |
| 6.3.4 | 19 / 11 | |
| 6.3.3 | 19 / 11 | |
| 6.3.2 | 19 / 11 | |
| 6.3.1 | 19 / 11 | |
| 6.3.0 | 19 / 11 | |
| 6.2.1 | 17 / 11 | |
| 6.2.0 | 17 / 11 | |
| 6.1.2 | 17 / 11 | |
| 6.1.1 | 17 / 11 | |
| 6.1.0 | 17 / 11 | |
| 6.0.4 | 17 / 11 | |
| 6.0.3 | 16 / 11 | |
| 6.0.2 | 16 / 11 | |
| 6.0.1 | 16 / 11 | |
| 6.0.0 | 16 / 11 |
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.