burnboard-cli@0.4.2
Connect local AI coding token usage to BurnBoard
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not an install-hook attack, but it provides an opaque remote tracker with persistence and modifies a foreign AI-tool configuration. The behavior is sufficiently risky and unresolved to warn rather than publish-block.
Decision evidence
public snapshot- The explicit connect and join flows install a tracker after authentication.
- The installer downloads an unpinned JavaScript agent from the service and runs it.
- The installer removes Claude telemetry settings and creates recurring sync and update jobs.
- Recurring updates invoke the latest release of this package without user interaction.
- package.json has no preinstall, install, or postinstall hook.
- The risky setup path is reached through an explicit CLI connection or setup command.
- The downloaded agent is not included in this snapshot, so its collection behavior cannot be verified directly.
Source & flagged code
6 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.2.
See all versions of burnboard-cli for other recorded verdicts.
- Review the evidence and your use of burnboard-cli@0.4.2 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.