ClawAudit verdict
tibber-energy
A Tibber energy API client that fetches electricity spot prices and optimizes appliance scheduling; uses a declared API token only against the documented Tibber API, with smart-home control commands requiring explicit --execute flag and defaulting to dry-run mode.
⚠ 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.
Findings (5)
Possible hardcoded credential
SKILL.md · code · TOKEN="your_tibber_token
subprocess execution — runs system commands from Python
tibber_energy.py · prose · downgraded · subprocess.run(
subprocess with shell=True — command injection vector
tibber_energy.py · prose · downgraded · subprocess.run(cmd, shell=True
Python urllib.request — network access
tibber_energy.py · prose · downgraded · urllib.request
Python os.environ.get — reads environment variable
tibber_energy.py · prose · downgraded · os.environ.get(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
Requires 1 environment variable. (1 sensitive: TIBBER_ACCESS_TOKEN). Requires 1 system binary.
Is this flag fair?
Thanks — recorded.