@1sat/cli@0.0.72
CLI for 1Sat Ordinals SDK
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic source inspection finds a package-aligned Bun prerequisite check and explicit wallet/MCP functionality, not a concrete malicious chain. The scanner’s lifecycle, network, and environment signals are explained by these declared CLI features.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install for the Bun check; explicit `1sat mcp-proxy` invocation for MCP relay
Impact
Package-owned wallet/config/key files may be created during explicit commands; no unconsented broad agent-control mutation or exfiltration is established.
Mechanism
Bun runtime probe and signed stdio-to-HTTP wallet MCP bridge
AI rationale
Static source inspection finds a package-aligned Bun prerequisite check and explicit wallet/MCP functionality, not a concrete malicious chain. The scanner’s lifecycle, network, and environment signals are explained by these declared CLI features.
Evidence
package.jsonscripts/check-bun.cjssrc/cli.tssrc/commands/mcp-proxy.tssrc/commands/serve.tssrc/commands/remote.tssrc/config.tssrc/keys.tssrc/commands/serve-messagebox.tssrc/repricer/whatsOnChain.tssrc/context.tssrc/monitor-lock.ts
Network endpoints3
127.0.0.1:3322api.1sat.app/1satapi.whatsonchain.com/v1/bsv
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- `package.json` runs `scripts/check-bun.cjs` as `preinstall`.
- `src/commands/mcp-proxy.ts` can relay stdin JSON-RPC to a configured MCP endpoint.
Evidence against
- `scripts/check-bun.cjs` only executes `bun --version`; it makes no writes or network calls.
- `src/cli.ts` dispatches runtime behavior only after explicit CLI invocation.
- `src/commands/mcp-proxy.ts` defaults to `http://127.0.0.1:3322` and writes only its own `~/.1sat-wallet/mcp-agent.key` with mode `0600`.
- All four source `fetch` calls are user-invoked MCP or service/price operations; no credential or environment harvesting/exfiltration path was found.
- No eval, VM, remote code loading, destructive filesystem action, or foreign AI-agent configuration mutation appears in inspected sources.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
1 flaggedpackage.jsonView file
•scripts.preinstall = node scripts/check-bun.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
1 High3 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @1sat/cli@0.0.72.
See all versions of @1sat/cli for other recorded verdicts.
- Review the evidence and your use of @1sat/cli@0.0.72 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.