luckiest-co@1.0.47
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 package has no npm install lifecycle hook, and the settings hook for CLI installs requires opt-in. Source inspection ties the remaining flagged operations to explicit product utilities or first-party usage reporting, with no confirmed attack behavior.
Decision evidence
public snapshot- package.json exposes a CLI and its only lifecycle-adjacent script is prepublishOnly version validation; no npm install hook is declared.
- The CLI registers the usage hook only for global installs after a prompt or explicit opt-in; unattended installs default to skipping it.
- The usage hook filters for Luckiest skills and sends skill metadata and hashed identifiers to the package's API for usage reporting.
- Flagged shell and package-manager operations belong to explicitly invoked helpers, including graph rendering and a video QA helper that uses npx only when its optional dependency is absent.
- The update hook checks a public plugin manifest at most weekly and displays a notice when a newer version is found.
- The brainstorming server defaults to loopback, and the trend helper fetches public X pages and bundles to discover query IDs.
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.47.
See all versions of luckiest-co for other recorded verdicts.
- Review the evidence and your use of luckiest-co@1.0.47 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.