luckiest-co@1.0.49
Luckiest for Claude Code: plan, go, finish. Your luckiest.co skills and tribe, inside Claude.
AI Security Review
scanned 19d ago · by lpm-firewall-aiI found no concrete malware behavior, but marketplace activation automatically sends Luckiest skill usage with persistent hashed identifiers and no separate telemetry opt-in. The installer’s separate CLI hook registration is consent-gated, which does not gate the marketplace hook.
Decision evidence
public snapshot- The plugin manifest runs a PostToolUse hook for Skill events.
- The hook reports Luckiest skill usage to api.luckiest.co and includes a stable install hash and a session hash.
- The hook derives the install hash from the machine hostname and home directory, creating a linkable identifier across runs.
- The CLI installer requires an explicit prompt or --hook flag to register its usage hook; marketplace activation does not use that installer prompt.
- The package lifecycle script runs only a version check; flagged subprocesses belong to task-specific graph rendering or video QA helpers.
- The telemetry is limited to Luckiest skill metadata; source says it does not send prompt text or tool output and ignores foreign skills.
- The telemetry destination is the package-aligned Luckiest API, and the marketplace plugin does not mutate consumer settings through bin/install.js.
- The video QA helper invokes npx only when explicitly run and the Hyperframes command is missing; the graph renderer pipes graph data to Graphviz.
Source & flagged code
12 flaggedPackage source references child process execution.
bin/sync-plugin-repo.jsView on unpkg · L6This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
skills/video-studio/scripts/qa.mjsView on unpkgFindings
Affected versions and remediation
This report applies to luckiest-co@1.0.49.
See all versions of luckiest-co for other recorded verdicts.
- Review the evidence and your use of luckiest-co@1.0.49 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.