Caveat verdict

dify-flow-access

45
🟠 Risky
Significant risk patterns flagged — automated deep scan, not behavioral proof.

The skill embeds a literal API key (`app-jUhDcPj3lcnEG04JW4gRsfyy`) and a private internal IP (`http://10.10.10.159/v1`) directly in its documentation, making credentials visible to anyone who can read the skill and coupling the config to a specific internal deployment in a way that is inappropriate for a shared skill.

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

25
security
30
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (3)

Pattern match critical

Possible hardcoded credential

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

Pattern match high

Pipe to python — executes piped content as Python code

scripts/dify-workflow.sh · prose · downgraded · | python3

Pattern match medium

HTTP request to bare IP address — common in malicious payloads

SKILL.md · prose · downgraded · http://10.10.10.159

Permissions & capabilities

No declared permissions — minimal attack surface.

network_incredential_access

Is this flag fair?

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