shakers-cli
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).
This report shows the evidence for shakers-cli@0.23.0. 0 of 12 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiNo malicious credential redirection or install-time behavior was identified. However, the default runtime audit sends hostname and OS username with command metadata when unauthenticated, which makes this undisclosed identifying telemetry suspicious.
Static reason
One or more suspicious static signals were detected.
Trigger
Ordinary CLI startup, unless SHAKERS_CLI_NO_AUDIT=1 is set.
Impact
The service can associate CLI activity with a local account name and machine hostname, even when the user has not signed in.
Mechanism
A detached worker posts the command, scrubbed arguments, CLI version and timestamp to the Shakers certifications service; without a valid session it adds the OS username and hostname.
AI rationale
No malicious credential redirection or install-time behavior was identified. However, the default runtime audit sends hostname and OS username with command metadata when unauthenticated, which makes this undisclosed identifying telemetry suspicious.
Evidence
bin/shakers.jsbin/command-audit-worker.js
Network endpoints1
api.certifications.shakersworks.com/api/v1/cli/command-log
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI starts command auditing during ordinary startup; auditing is disabled only by setting SHAKERS_CLI_NO_AUDIT=1.
- Audit records include the command, scrubbed arguments, CLI version and timestamp.
- When no valid session token is available, the record also includes the OS username and hostname.
- Records are posted to the package’s Shakers certifications service; shakers-cli maps to the production profile, whose base is https://api.certifications.shakersworks.com/api/v1.
- The manifest declares a CLI binary and no lifecycle scripts.
Evidence against
- The audit sends to the package’s own service, and authenticated requests use the user’s Shakers session token.
- The separate superadmin password flow requires running that command and prompts for the password; its endpoint derives from the configured ingest service.
- Audit arguments are scrubbed, and the code removes one-time login codes before logging.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
6 flaggedbin/shakers.jsView file
35"use strict";
L36: var import_child_process = require("child_process");
L37: function langFromLocaleString(raw) {
High
17445return {
L17446: linkedin: uniq((t.match(/(?:https?:\/\/)?(?:[a-z]{2,3}\.)?linkedin\.com\/in\/[A-Za-z0-9_%-]+/gi) || []).map((u) => `https://www.${u.replace(/^https?:\/\//i, "").replace(/^(?:[a-z]{...
L17447: github: uniq((t.match(/(?:https?:\/\/)?github\.com\/[A-Za-z0-9-]+/gi) || []).map((u) => `https://${u.replace(/^https?:\/\//i, "")}`)),
...
L17451: }
L17452: function readCvText(input, { platform = process.platform, exec = import_child_process.execFileSync, env = process.env, talentName = null } = {}) {
L17453: const file = (0, import_env_paths.expandHome)(input, env);
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/shakers.jsView on unpkg · L17445•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
bin/shakers.js:
{ type: "projectPath", path: ".claude" },
{ type: "homePath", path: ".claude" },
{ type: "vscodeExt", prefix: "saoudrizwan.claude-dev" }
{ type: "homePath", path: ".codex" },
return env.CODEX_HOME || require("path").join(getHomeDir(env), ".codex");
function writeFilePreservingMode(dest, buf, mode, overwrite) {
if (writeFilePreservingMode(dest, buf, st.mode & 511, isConfig)) brought.push(name);
fs.writeFileSync(marker, `${(/* @__PURE__ */ new Date()).toISOString()}
Findings
4 High3 Medium5 Low
HighChild Processbin/shakers.js
HighSame File Env Network Executionbin/shakers.js
HighCredential Redirect Persistencebin/shakers.js
HighCross File Remote Execution Contextbin/mcpb.js
MediumDynamic Requirebin/shakers.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptobin/shakers.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to shakers-cli@0.23.0.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of shakers-cli@0.23.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.