Run a FlareDeck agent on your own machine: it picks up cards assigned to it, works each one in a checkout of its own, and reports back on the card.
Allowed — no malicious behavior detected
19 low-signal patterns reviewed and cleared.
AI security review
scanned · by lpm-firewall-ai
The manifest has no install-time hook, and the flagged command execution is part of the package's remote-management feature: requests are claimed through the configured FlareDeck service and results are returned there. Setup and tmux configuration writes support the CLI's stated use and are bounded to explicit setup or relevant tmux conditions.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI starts the agent; remote execution requires a manager request, while setup is an explicit command.
Impact
Commands requested through the manager run as the local user. The reviewed flow returns their output to the configured FlareDeck service.
Mechanism
The agent claims manager requests through its configured FlareDeck service, runs the command locally, and posts its result back. A local switch disables remote commands.
Evidence
~/.tmux.confselected shell profile (such as ~/.zshrc or ~/.bashrc)
Network endpoints2
configured FlareDeck service originregistry.npmjs.org
Decision evidence
public snapshot
Evidence for AI clean decision
The manifest exposes a CLI and declares no install hook; its only lifecycle script is prepublishOnly.
Remote commands are claimed through the configured FlareDeck service using the agent's authorization.
A command runs only after a request is claimed, and its output is returned to FlareDeck as the command result.
Users can disable remote commands with a local switch that FlareDeck cannot remove.
The setup command writes a shell profile only when explicitly run; tmux scrollback configuration is limited to an active tmux session where mouse mode is off.
Startup updates check npm for newer versions of this package.
Evidence against
Behavioral surface
SourceChild process · Crypto · Environment variables · Eval · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestNo license
Scanned 131 files · 1.60 MB of source
14 external domains referenced
127.0.0.1
api.github.com
app.flaredeck.app
flaredeck-agent-861259873190.us-central1.run.app
generativelanguage.googleapis.com
github.com
jam.dev
mcp.cnjure.design
mcp.flaredeck.app
mcp.jam.dev
mcp.sceneflo.ai
openrouter.ai
pypi.org
registry.npmjs.org
Findings
6 high · 5 medium · 8 low
Automated scan signals; the review checked them and cleared this version. Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
382 { type: 'text', text: `This is the screen at ${viewport.width}×${viewport.height}. Judge only what is plain to see; never give a size in pixels.${takeStuckNote()}` },
31// npx puts npm[redacted] in the environment, and the environment beats the config FILE
32// we just wrote — which is why `npm config set prefix` appeared to work and the install
⋯
58functionshellProfile() {
59const home = homedir();
60const shell = process.env['SHELL'] ?? '';
61const candidates = shell.includes('zsh')
62 ? ['.zshrc', '.zprofile', '.profile']
63 : ['.bashrc', '.bash_profile', '.profile'];
'ssh -o BatchMode=yes'
'never'
35});
⋯
44}
45/** `https://github.com/Owner/Repo(.git)` → `owner__repo`: the clone's folder name. */