@computesdk/browseruse
Browser Use Cloud browser provider for ComputeSDK - cloud browser sessions with stealth mode, residential proxies, profiles, and session recording
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:dotenv | AI (phantom-deps): dotenv declared as dep but used via config/env loading pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:computesdk | AI (phantom-deps): computesdk is a sibling monorepo package; phantom-dep heuristic fires on indirect usage patterns. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 5 / 8 | |
| 0.2.3 | 5 / 8 | |
| 0.2.2 | 5 / 8 | |
| 0.2.1 | 5 / 8 | |
| 0.2.0 | 5 / 8 |
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.