ClawAudit verdict

bitget-data

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

Bitget grid trading system storing credentials in a local JSON config and making API calls to the Bitget exchange; hardcoded file paths with another user's home directory are sloppy documentation artifacts, not evidence of exfiltration.

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

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

63
security
40
transparency
70
maintenance

Findings (5)

Pattern match high

HTTP request to bare IP address — common in malicious payloads

README.md · code · http://127.0.0.1

Pattern match medium

References child_process — can spawn system processes

bitget-cli.js · prose · downgraded · child_process

Pattern match low

Node http/https module — low-level network access

analyze-coins.js · prose · downgraded · require('https')

Pattern match low

Accesses sensitive environment variables

analyze-coins.js · prose · downgraded · process.env.BITGET_API_KEY

Pattern match low

References agent configuration files

multi_agent_controller.js · prose · downgraded · agent_config

Why the tier is capped

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

Is this flag fair?

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