registry / savant-code / 0.0.32
savant-code@0.0.32
Multi-Agent AI Coding Assistant with ECHO Protocol
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source shows a CLI wrapper that fetches and runs SavantCode release binaries, with staged updates requiring interactive approval before installation. Optional failure telemetry requires an environment-configured PostHog key and host; no malicious data flow or unrelated execution was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI; update checks follow launch, and installation of a staged update requires interactive approval.
Impact
No malicious impact identified. Configured failure telemetry may include the local config path in its identifier and an error message.
Mechanism
The launcher fetches release assets from the project’s GitHub releases and starts the installed SavantCode binary. Failure telemetry is conditional on environment-provided PostHog credentials and host.
AI rationale
The source shows a CLI wrapper that fetches and runs SavantCode release binaries, with staged updates requiring interactive approval before installation. Optional failure telemetry requires an environment-configured PostHog key and host; no malicious data flow or unrelated execution was identified.
Evidence
~/.config/savant/savant-code~/.config/savant/savant-code-metadata.json~/.config/savant/.download-temp
Network endpoints3
registry.npmjs.orggithub.com (savant0x/savant-code releases)Host supplied by SAVANT_CODE_POSTHOG_HOST or NEXT_PUBLIC_POSTHOG_HOST_URL
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes `index.js` as its CLI; importing it creates a launcher, while `launcher.main()` runs only when invoked as the main module.
- The launcher downloads release assets from the SavantCode GitHub releases host, consistent with this package’s binary-launcher purpose.
- A staged update is offered for installation only after an interactive approval.
- Failure telemetry requires both an API key and host from environment variables and is called on download or platform-check failures.
Evidence against
- When enabled, failure telemetry includes an identifier derived from the local config directory and the error message.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedlauncher.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = savant-code@0.0.22
matchedIdentity = npm:c2F2YW50LWNvZGU:0.0.22
similarity = 0.667
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
launcher.jsView on unpkg2L3: const { spawn, execFileSync } = require('child_process')
L4: const crypto = require('crypto')
High
index.jsView file
2L3: const fs = require('fs')
L4: const path = require('path')
Medium
Findings
1 Critical4 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltalauncher.js
HighChild Processlauncher.js
HighSame File Env Network Executionlauncher.js#virtual:normalized:round1
HighCommand Output Exfiltrationlauncher.js#virtual:normalized:round1
HighSemantic Analysis Limitedlauncher.js#virtual:normalized:round1
MediumDynamic Requireindex.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to savant-code@0.0.32.
See all versions of savant-code for other recorded verdicts.
- Review the evidence and your use of savant-code@0.0.32 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.