browserstack-local
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:temp-fs | AI (phantom-deps): temp-fs is a declared dependency used indirectly; phantom-dep heuristic fires but no real risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established official BrowserStack package; lack of provenance is common and not a risk signal here. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): browserstack-local inherently spawns a local binary via child_process; this is core to its documented functionality. | ai | |
| phantom-deps | phantom-dep:agent-base | AI (phantom-deps): agent-base is a transitive/indirect dep used via https-proxy-agent; phantom-dep false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.5.13 | 4 / 9 | |
| 1.5.12 | 4 / 9 | |
| 1.5.11 | 4 / 9 | |
| 1.5.10 | 4 / 9 |
v1.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.