@computesdk/browserbase
Browserbase browser provider for ComputeSDK - cloud browser sessions with stealth mode, proxies, and session replay
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 is a transitive dependency used in config; stable for this package type. | ai | |
| phantom-deps | phantom-dep:computesdk | AI (phantom-deps): computesdk is a peer/framework dependency; stable for this provider package. | ai | |
| phantom-deps | phantom-dep:playwright-core | AI (phantom-deps): playwright-core is used indirectly through @browserbasehq/sdk; stable for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.3.7 | 5 / 8 | |
| 0.3.6 | 5 / 8 | |
| 0.3.5 | 5 / 8 | |
| 0.3.4 | 5 / 8 | |
| 0.3.3 | 5 / 8 | |
| 0.3.2 | 5 / 8 | |
| 0.3.1 | 5 / 8 | |
| 0.3.0 | 5 / 8 | |
| 0.2.0 | 5 / 8 |
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
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.