Caveat verdict

fatsecret-api

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

Requires client ID/secret to call FatSecret API, a standard integration pattern without hidden exfiltration.

⚠ 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.

98
security
100
transparency
90
maintenance

Findings (2)

Coarse signal — prose, single-step high

Instruction-prose smuggling shape detected: collects a sensitive target ("credentials") and emits it outward ("POST"). Phrased as prose with no trigger tokens — a semantic prompt-injection / data-exfil pattern the syntactic scanners can't see. Final tier capped at Caution; review the instructions before installing.

SKILL.md · | Endpoint | Method | Data sent | |---|---|---| | `https://platform.fatsecret.com/rest/v2/server.api` | POST | OAuth 2.0 bearer-token authorized requests: metho

Pattern match low

Python os.environ.get — reads environment variable

scripts/fs_runner.py · prose · downgraded · os.environ.get(

Permissions & capabilities

Requires 2 environment variables. (2 sensitive: FATSECRET_CLIENT_ID, FATSECRET_CLIENT_SECRET). Requires 1 system binary.

Is this flag fair?

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