registry / @crbonfree/cli / 0.2.3
@crbonfree/cli@0.2.3
See the carbon footprint of your AI coding agents, and give them a shared memory across every tool.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed credential flow uses the configured server, defaulting to the package's own Crbon API. The network and persistence behavior is consistent with the CLI's stated sign-in, usage-sync, and onboarding functions.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs a CLI command such as install or sync; recurring sync can be configured during onboarding.
Impact
Expected service authentication and agent usage syncing; no evidence of credential forwarding to an unrelated host.
Mechanism
The CLI reads credentials from environment variables or saved configuration and uses the configured server URL for service requests. The default backend is api.crbonfree.com.
AI rationale
The manifest has no install lifecycle hook, and the reviewed credential flow uses the configured server, defaulting to the package's own Crbon API. The network and persistence behavior is consistent with the CLI's stated sign-in, usage-sync, and onboarding functions.
Network endpoints1
api.crbonfree.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest lists build and development scripts, with no install, preinstall, or postinstall lifecycle script.
- The API key and server URL come from the user's environment or saved configuration; the default backend is api.crbonfree.com.
- The CLI sends the key to the configured server's memory configuration endpoint and rejects redirects.
- The install command is described as onboarding with sign-in, scheduler setup, and a first sync; the sync command describes its upload as local coding-agent token usage.
Evidence against
- The package exposes CLI commands and hook installers that can access agent session data when used.
- The install command can set up recurring sync after sign-in, and memory setup is offered during onboarding.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
13 flaggeddist/updateBin.jsView file
455// src/openBrowser.ts
L456: import { execFile } from "child_process";
L457: import { readFileSync as readFileSync6 } from "fs";
High
Child Process
Package source references child process execution.
dist/updateBin.jsView on unpkg · L455686const modPath = "./openclawPlugin.js";
L687: const mod = await import(modPath);
L688: if (typeof mod.installOpenClawPlugin === "function") {
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/updateBin.jsView on unpkg · L686dist/mechanisms/compressCliBin.jsView file
496const result = spawnSync(command, {
L497: shell: true,
L498: encoding: "utf-8",
High
Shell
Package source references shell execution.
dist/mechanisms/compressCliBin.jsFindings
10 High5 Medium5 Low
HighChild Processdist/updateBin.js
HighShelldist/mechanisms/compressCliBin.js
HighSame File Env Network Executiondist/proxyServerBin.js
HighCredential Redirect Persistencedist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighSandbox Evasion Gated Capabilitydist/proxyServerBin.js
HighExternal Ai Agent Control Surface Mutationdist/cli.js
HighTrigger Reachable Command Output Exfiltrationdist/cli.js
HighTrigger Reachable Persistencedist/cli.js
HighSemantic Analysis Limiteddist/hooks/installerBin.js#virtual:normalized:round1
MediumDynamic Requiredist/updateBin.js
Medium
Affected versions and remediation
This report applies to @crbonfree/cli@0.2.3.
See all versions of @crbonfree/cli for other recorded verdicts.
- Review the evidence and your use of @crbonfree/cli@0.2.3 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.