luzra-cli@0.1.12
터미널 AI(Claude Code) 프롬프트 습관을 채점·코칭하는 리포트 — 세션 로그는 로컬에서만 분석됩니다.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource establishes an explicit-user scheduled, self-updating analytics agent with remotely supplied instructions, but not malicious install-time mutation, exfiltration of raw prompts, or covert payload execution. Warn rather than block.
Decision evidence
public snapshot- src/init.js installs a daily OS scheduler after interactive init.
- src/install.js self-updates global luzra-cli from npm during reports.
- src/engine.js sends server-supplied judge instructions to local `claude -p`.
- src/sync.js uploads score/profile data after dashboard connection.
- package.json has no lifecycle scripts.
- All persistence is reached from explicit `luzra init`, not installation.
- Session prompts are masked before being passed to the judge.
- No hidden payload, eval, credential harvesting, or foreign agent-config writes found.
Source & flagged code
6 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
src/connect.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to luzra-cli@0.1.12.
See all versions of luzra-cli for other recorded verdicts.
- Review the evidence and your use of luzra-cli@0.1.12 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.