Caveat verdict

starling-home-hub

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

Controls local Nest smart-home devices via the Starling Home Hub local REST API using a user-provided API key in an env var; all commands serve the stated device control 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.

70
security
60
transparency
70
maintenance

Findings (1)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY="your-api-key

Why the tier is capped

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