luzra-cli@0.2.7
터미널 AI(Claude Code) 프롬프트 습관을 채점·코칭하는 리포트 — 세션 로그는 로컬에서만 분석됩니다.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has a legitimate scoring and dashboard-sync purpose, and the diagnostic data is partially sanitized and sent to the configured dashboard. However, it also sends a separate, undocumented stream of runtime error details, so this merits a warning for undisclosed telemetry.
Decision evidence
public snapshot- The CLI posts run diagnostics to the configured dashboard's `/api/runs` endpoint when a sync URL and token are present.
- The diagnostics include run status and summarized error details; messages are masked, the home directory is replaced, and each detail is capped at 200 characters.
- `report` sends diagnostics after a run and also sends a summary on crashes, including during scheduled runs.
- The README describes dashboard uploads of scoring reports and prompt handling, but does not disclose this separate error-reporting request.
- The diagnostics go to the user-configured dashboard and use its token; they are not sent to an unrelated collector.
- Error messages are masked, home paths are replaced, and message details are truncated.
- Dashboard connection is a user-confirmed step in `init`, and the scheduler is installed as part of that documented setup.
Source & flagged code
8 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.2.7.
See all versions of luzra-cli for other recorded verdicts.
- Review the evidence and your use of luzra-cli@0.2.7 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.