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 flagged shell execution is a FlareDeck manager command flow: requests are claimed with the agent's authentication, can be refused by a local switch, and results return to FlareDeck. The manifest has no install hook, and the setup and shell-profile changes are reached through an explicit setup command.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user starts the agent; remote commands are triggered by FlareDeck manager events and the machine can disable them locally.
Impact
The manager can run commands as the agent's user when remote commands are enabled; this capability matches the package's managed-agent purpose.
Mechanism
The agent claims commands using its configured FlareDeck authentication, runs them in its working directory, and posts results back to FlareDeck.
Network endpoints2
Configured FlareDeck origin: /api/v1/{tenantId}/exec/{id}/claim and /resultregistry.npmjs.org (startup update check)
Decision evidence
public snapshot
Evidence for AI clean decision
The manifest has no install, preinstall, or postinstall hook; its only lifecycle script is prepublishOnly.
The package describes its purpose as running a FlareDeck agent that works assigned cards and reports back.
Remote commands arrive as FlareDeck events and are handled only when the agent has an authenticated tenant and event message.
The command handler claims each request through the agent API before running it, and can refuse commands when the machine-level remote switch is off.
Command results are returned through the same FlareDeck API used by the feature.
Evidence against
The remote command feature runs manager-supplied shell commands as the agent's user, with the agent's working directory.
The remote command switch is on unless the user turns it off locally.
On startup, the launcher checks npm for a newer release and may update and relaunch itself.
Behavioral surface
SourceChild process · Crypto · Environment variables · Eval · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestNo license
Scanned 130 files · 1.58 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.