luzra-cli
터미널 AI(Claude Code) 프롬프트 습관을 채점·코칭하는 리포트 — 세션 로그는 로컬에서만 분석됩니다.
This report shows the evidence for luzra-cli@0.3.0. 0 of 9 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source supports the package's stated purpose: analyzing Claude Code sessions and optionally syncing results to a dashboard. Scheduler setup is called from init, and network use is tied to the configured dashboard or npm's registry; no malicious behavior was identified.
Decision evidence
public snapshot- The manifest declares no lifecycle scripts; it describes local analysis of Claude Code session logs.
- Dashboard connection is offered during init and requires confirmation before connecting.
- Daily scheduling is installed by the init flow, and the scheduled task runs the package's report command.
- Profile sync uses the configured dashboard URL and token; its source says prompt text stays local.
- Self-updates are checked against the official npm registry during report runs.
- The package creates a persistent daily task and can update its global installation at runtime, but the source ties these actions to user-run CLI workflows.
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.3.0.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of luzra-cli@0.3.0 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.