Caveat verdict

python-sdk-best-practices

brightdata-python-sdk-best-practices

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Best practices guide for the Bright Data Python SDK for web scraping; reads BRIGHTDATA_API_TOKEN from environment and makes standard SDK calls matching the stated web scraping documentation purpose.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

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.

30
security
60
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="your_token

Pattern match medium

Popular HTTP library — network access

SKILL.md · code · Got

Pattern match medium

Opens WebSocket connection

references/api-reference.md · code · WebSocket

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class 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.

package_installnetwork_out

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API