Caveat verdict
bright-data-best-practices
brightdata-bright-data-best-practices
Accesses credentials AND makes external network calls
Reference documentation for Bright Data API integrations (Web Unlocker, SERP, Browser API); credential usage is standard API key auth to the documented Bright Data endpoints, consistent with the stated purpose.
Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
What it does
These are capability combinations: each listed behavior occurs in the skill, but Caveat detects co-occurrence — it does not verify that one flows into another. Read the code to confirm a live chain.
Accesses credentials AND makes external network calls — potential credential theft
LLM02 · ASI03
Permission integrity
network_out
credential_access
Findings (9)
Possible hardcoded credential
SKILL.md · code · API_KEY="your-api-key
Pipe-to-shell pattern (curl | sh) — supply chain attack vector
references/cli-setup.md · code · curl -fsSL https://cli.brightdata.com/install.sh | bash
Pipe to bash — executes piped content as shell commands
references/cli-setup.md · code · | bash
Accesses process.env — reads environment variables
SKILL.md · code
POSTs data to external URL
SKILL.md · code · .post(
"https://
Accesses sensitive environment variables
SKILL.md · code · process.env.BROWSER_AUTH
Base64 encoding/decoding
references/browser-api.md · code · base64-encode
Opens WebSocket connection
references/browser-api.md · prose · downgraded · WebSocket
Makes HTTP request to external URL
references/serp-api.md · code · fetch("https://
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
No declared permissions — minimal attack surface.
credential_accessnetwork_out Thanks — recorded.