← Home

@browserbasehq/sdk

npm Repository Homepage
29
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

seanmcguire12kylejeongnosajzerofooldesaadiajmcquilkinmiguel_gbrowserz

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): playwright-core is a well-established Microsoft package directly relevant to this browser automation SDK, which already depended on puppeteer-core. Addition is expected and benign. ai
source-diff source-size-tripled AI (source-diff): Size increase is explained by the addition of a browser build target (build:browser script + browserify in devDeps), producing many new compiled output files. ai
source-diff large-new-source-files AI (source-diff): 36 new files consistent with browser build target output; no signs of injected or obfuscated code. ai
provenance publisher-changed AI (provenance): maxbeatty is a long-standing npm account (9+ years, 144 approved packages) taking over from mishushakov; consistent with legitimate org handoff to Browserbase company account. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Auto-generated SDK pattern; @types/node is a conventional runtime dep in this SDK style, not a security concern. ai
phantom-deps phantom-dep:@types/node-fetch AI (phantom-deps): Auto-generated SDK pattern; @types/node-fetch is a conventional runtime dep in this SDK style, not a security concern. ai

Versions (showing 29 of 29)

Show 2 prereleases
Version Deps Published
2.11.0 7 / 0
2.10.0 7 / 0
2.9.0 7 / 0
2.8.0 7 / 0
2.7.0 7 / 0
2.6.0 7 / 0
2.5.0 7 / 0
1.5.0 3 / 6
1.4.4 3 / 6
1.4.3 3 / 6
1.4.2 2 / 4
1.4.1 2 / 4
1.4.0 2 / 4
1.3.1 2 / 4
1.3.0 2 / 4
1.2.1 2 / 4
1.2.0 2 / 4
1.1.9 2 / 4
1.1.8 2 / 4
1.1.7 2 / 4
1.1.6 2 / 4
1.1.5 2 / 4
1.1.4 2 / 4
1.1.3 2 / 4
1.1.2 2 / 4
1.1.1 2 / 4
1.1.0 2 / 4
1.0.1 2 / 4
1.0.0 2 / 4

v2.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anirudhkamath.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

2 findings
HIGH Publisher changed: mishushakov → maxbeatty (on 2024-06-08) provenance

This version was published by a different npm account than previous versions on 2024-06-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

2 findings
HIGH Publisher changed: mishushakov → maxbeatty (on 2024-06-07) provenance

This version was published by a different npm account than previous versions on 2024-06-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.