savant-code@0.0.34
Multi-Agent AI Coding Assistant with ECHO Protocol
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe launcher sends a local path in runtime telemetry without a clear disclosure in the inspected package files. This requires PostHog environment configuration and occurs on update failure, so the finding warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An update failure occurs while a PostHog API key and host are set in the environment.
Impact
The receiving analytics host can associate an update failure with a local filesystem path.
Mechanism
The launcher includes os.homedir() in the telemetry distinct_id and POSTs the event to the configured host.
AI rationale
The launcher sends a local path in runtime telemetry without a clear disclosure in the inspected package files. This requires PostHog environment configuration and occurs on update failure, so the finding warrants a warning rather than a block.
Evidence
launcher.js~/.config/savant
Network endpoints3
PostHog host configured by SAVANT_CODE_POSTHOG_HOST or NEXT_PUBLIC_POSTHOG_HOST_URLregistry.npmjs.orggithub.com/savant0x/savant-code/releases/download
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Failure telemetry is enabled when both a PostHog API key and host are present in environment variables.
- The event payload uses the local home-directory path as its distinct_id.
- Update failure events are POSTed to the configured PostHog host.
- The launcher invokes update checks after startup, and download failures call the telemetry function.
Evidence against
- The telemetry path requires explicit PostHog environment configuration; no default API key or host is supplied in the launcher.
- The launcher stages updates and asks for approval before installing them.
- Version checks and binary downloads use npm and the package's GitHub release host.
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.34.
See all versions of savant-code for other recorded verdicts.
- Review the evidence and your use of savant-code@0.0.34 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.