@skillsmith/cli@0.8.11
A registry for sharing, scanning, and tracking agent skills across teams.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe install-event code sends usage telemetry by default when a Skillsmith API key is available, while the README says analytics require explicit opt-in. The event contains skill metadata and a hashed key identifier, not the raw credential, so this is suspicious telemetry rather than credential exfiltration.
Decision evidence
public snapshot- README.md says anonymous product analytics are opt-in and disabled by default, requiring SKILLSMITH_TELEMETRY_ENABLED=true.
- The bundled install-event sender checks SKILLSMITH_TELEMETRY only for opt-out values and sends when an API key is available.
- The CLI invokes that sender after skill installation, including skill ID, source, success, duration, trust tier, and error code.
- The event uses a keyed hash of the Skillsmith API key as its anonymous ID and targets the Skillsmith events endpoint.
- The install event does not include the raw API key; it uses an HMAC-derived identifier and sends skill-install metadata.
- The separate Claude Code hook template requires telemetry.enabled=true before sending invocation events.
- The manifest exposes a CLI executable and has no install lifecycle hook; prepublishOnly is a publish-time script.
Source & flagged code
12 flaggedSource appears to send environment or credential material to an external endpoint.
dist/cli.jsView on unpkg · L50Findings
Affected versions and remediation
This report applies to @skillsmith/cli@0.8.11.
See all versions of @skillsmith/cli for other recorded verdicts.
- Review the evidence and your use of @skillsmith/cli@0.8.11 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.