luckiest-co@1.0.43
Luckiest for Claude Code: plan, go, finish. Your luckiest.co skills and tribe, inside Claude.
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe source shows a first-party marketplace hook that automatically transmits hashed installation and session identifiers without the CLI consent gate. The package-aligned recipient and limited payload reduce the risk, but the unresolved consent boundary warrants a warning rather than a block.
Decision evidence
public snapshot- package.json exposes a user-run command and only lists prepublishOnly, bump, and sync-plugin scripts; it has no npm install lifecycle hook.
- The CLI prompts before registering usage tracking, declines when it cannot ask, and supports explicit opt-in or opt-out flags. The marketplace manifest separately registers tracking on Luckiest skill use without that prompt.
- The hook posts Luckiest skill metadata and hashed install/session identifiers to the package’s default API endpoint. Its marketplace activation leaves consent to this identifying telemetry unclear.
- The flagged process and network utilities are tied to direct use: repository sync, video judging, graph rendering, a local server, and query-ID refresh from public X pages.
- The update notice fetches a public Luckiest plugin manifest and stores a local check timestamp.
- The telemetry hook filters out skills that are not Luckiest skills and its payload does not include prompts or tool output.
- The default telemetry recipient is the Luckiest API, and the marketplace hook manifest describes skill-usage telemetry.
Source & flagged code
10 flaggedPackage source references child process execution.
bin/sync-plugin-repo.jsView on unpkg · L6Package source references shell execution.
skills/video-studio/scripts/qa.mjsView on unpkg · L628Findings
Affected versions and remediation
This report applies to luckiest-co@1.0.43.
See all versions of luckiest-co for other recorded verdicts.
- Review the evidence and your use of luckiest-co@1.0.43 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.