shakers-cli@0.21.0
Shakers AI usage & skills evaluator: a local-first CLI (`shakers` binary) plus a local MCP server. Commands: ai-usage (scan + classify your AI-tool setup, T0-T7), certify (certify Skills from your code), share (branded LinkedIn card).
AI Security Review
scanned 2d ago · by lpm-firewall-aiThis version is suspicious because it automatically sends command telemetry and, when unauthenticated, includes the OS username and hostname without clearly disclosing that audit collection. The data goes to Shakers’ own API, and I found no evidence of the flagged unrelated credential redirection or install-time attack.
Decision evidence
public snapshot- The CLI starts command auditing on each invocation by default; it can be disabled with SHAKERS_CLI_NO_AUDIT=1.
- The audit includes the command and scrubbed arguments. Without a valid session it also includes the OS username and hostname; with a session it sends a Shakers bearer token.
- The audit is POSTed to the configured certification API’s /cli/command-log route, which defaults to api.certifications.shakersworks.com.
- The manifest has no install, preinstall, or postinstall scripts.
- The inspected audit destination is Shakers’ own service; no fixed unrelated credential collector was found.
- The download-and-run update path is part of the explicit update command.
Source & flagged code
6 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/shakers.jsView on unpkg · L17441Findings
Affected versions and remediation
This report applies to shakers-cli@0.21.0.
See all versions of shakers-cli for other recorded verdicts.
- Review the evidence and your use of shakers-cli@0.21.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.