Caveat verdict
alpaca-py-cli
Alpaca trading CLI that defaults to paper trading ($100k virtual) and explicitly requires user consent before running 'alpaca auth' which saves keys to shell config; security considerations are transparently documented and the skill instructs agents to get explicit user permission before modifying shell config files.
⚠ 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.
Permission integrity
package_install
Findings (4)
Possible hardcoded credential
SKILL.md · code · API_KEY="your_api_key
Accesses shell history/config
SKILL.md · frontmatter · ~/.zshrc
Pipe to python — executes piped content as Python code
README.md · prose · downgraded · | Python
pip3 install — installs Python packages at runtime
SKILL.md · frontmatter · pip3 install
Permissions & capabilities
Requires 3 environment variables. (2 sensitive: ALPACA_API_KEY, ALPACA_SECRET_KEY). Requires 1 system binary.
package_install Is this flag fair?
Thanks — recorded.