burnboard-cli@0.4.0
Connect local AI coding token usage to BurnBoard
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package creates a persistent remotely controlled token-tracking agent and mutates a third-party AI tool configuration, but only after an explicit CLI action. The absence of lifecycle hooks prevents a malicious install-time verdict.
Decision evidence
public snapshot- The user-invoked setup downloads a remote tracker into the user profile and then runs it.
- Setup removes telemetry-related settings from Claude Code's settings file.
- Setup persists the remotely supplied tracker on a five-minute schedule and self-updates daily from the latest package version.
- The manifest has no preinstall, install, or postinstall hook.
- The behavior is reached through explicit CLI commands, not package installation.
- The bundled source names its default service endpoint and contains no direct credential harvesting or exfiltration implementation.
Source & flagged code
7 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
cli.mjsView on unpkg · L4Findings
Affected versions and remediation
This report applies to burnboard-cli@0.4.0.
See all versions of burnboard-cli for other recorded verdicts.
- Review the evidence and your use of burnboard-cli@0.4.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.