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
20 low-signal patterns reviewed and cleared.
AI security review
scanned · by lpm-firewall-ai
The command execution and output return are tied to claimed manager requests through the configured FlareDeck service, with a local opt-out. The other flagged behavior is the package's own npm updater and user-invoked setup; no unrelated collection or harmful automatic action was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The agent checks for updates on startup; remote commands run when a FlareDeck `exec` event arrives and the command is claimed; setup runs only through the explicit setup command.
Impact
These features let the agent work assigned tasks, support manager-issued commands, and update itself. A local switch refuses remote commands.
Mechanism
Remote commands are claimed through the configured FlareDeck API using the agent's token, run in the configured repository, and their output is returned to that API. The updater checks npm for this package's own releases.
The manifest describes a FlareDeck agent that works assigned cards on the user's machine.
Remote execution is triggered by a FlareDeck `exec` event; the event carries an ID and the command is claimed from FlareDeck.
The handler runs the claimed command locally and sends its exit code and output to the configured FlareDeck API.
The machine can disable remote commands locally with `flaredeck-agent remote off`.
The updater checks npm for this package's newer versions and installs the package itself.
The setup command is explicitly routed through `npx ... setup`; the only lifecycle script is `prepublishOnly`.
Evidence against
Behavioral surface
SourceChild process · Crypto · Environment variables · Eval · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestNo license
Scanned 132 files · 1.63 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
1 critical · 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. */