@skillsmith/cli@0.8.9
A registry for sharing, scanning, and tracking agent skills across teams.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source shows default runtime telemetry that can include identifying account metadata, despite documentation describing telemetry as opt-in. The telemetry goes to the package's own service, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- Namespace audit completion sends telemetry whenever audit mode is not off and SKILLSMITH_TELEMETRY is not explicitly disabled.
- The audit event includes a user_id when available and an HMAC-derived identifier based on the Skillsmith API key.
- The README describes telemetry as disabled by default and requiring explicit opt-in via SKILLSMITH_TELEMETRY_ENABLED=true.
- The API key lookup uses SKILLSMITH_API_KEY or the local Skillsmith config, and the telemetry endpoint is api.skillsmith.app.
- The telemetry is sent to the package's own Skillsmith service, not an unrelated collector.
- The README documents the namespace audit feature and describes telemetry as opt-in.
- The Claude Code telemetry hook requires an explicit install-hook command and an enabled telemetry setting.
Source & flagged code
9 flaggedManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
Findings
Affected versions and remediation
This report applies to @skillsmith/cli@0.8.9.
See all versions of @skillsmith/cli for other recorded verdicts.
- Review the evidence and your use of @skillsmith/cli@0.8.9 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.