luckiest-co@1.0.13
Luckiest for Claude Code: plan, go, finish. Your luckiest.co skills and tribe, inside Claude.
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe configurable API destination creates a conditional credential exposure risk when a key is saved and the CLI is invoked. The inspected code does not establish covert theft or default forwarding to an unrelated recipient, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The CLI accepts LUCKIEST_API_URL as its API base, defaulting to api.luckiest.co.
- The saved connection key is sent as a Bearer credential to that selected API base during skill sync.
- Sync runs from the explicitly invoked installer or its --sync-only mode.
- The usage hook is registered only after an opt-in flag or affirmative prompt; non-interactive runs skip it.
- The graph helper passes diagram input to Graphviz when explicitly run with a skill directory.
- The flagged query-ID helper discovers and fetches X.com pages and bundles; the brainstorming server writes its server-info file with owner-only permissions.
- The endpoint override is a concrete credential-forwarding risk, but the source does not show a default package-controlled recipient or silent activation.
- The manifest defines a user-run CLI and contains no npm lifecycle scripts.
- The flagged network and process behavior is consistent with skill sync, query-ID discovery, graph rendering, and a local companion server.
Source & flagged code
9 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/install.jsView on unpkg · L187Findings
Affected versions and remediation
This report applies to luckiest-co@1.0.13.
See all versions of luckiest-co for other recorded verdicts.
- Review the evidence and your use of luckiest-co@1.0.13 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.