files.com@1.2.779
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install hooks, and the inspected entry points perform Files.com SDK and explicitly invoked CLI or download work. The large generated model file is unusual in size, but the examined content is consistent with AutomationLog model code and revealed no attack behavior.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
API calls or file download methods invoked by the consuming application; the CLI wrapper runs when explicitly invoked.
Impact
Expected SDK API access and requested downloads; no automatic data collection or unrelated side effects were identified.
Mechanism
SDK requests use the configured Files.com API base URL and key. File download helpers fetch a supplied URL and write to a supplied destination; authentication headers are stripped across origins.
AI rationale
The manifest has no install hooks, and the inspected entry points perform Files.com SDK and explicitly invoked CLI or download work. The large generated model file is unusual in size, but the examined content is consistent with AutomationLog model code and revealed no attack behavior.
Evidence
caller-supplied download destination
Network endpoints2
app.files.comcaller-supplied HTTPS URL
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the Files.com SDK entry points and declares no install lifecycle scripts.
- The npm scripts build, test, lint, or watch the project; none is an install hook.
- The CLI wrapper runs only when invoked and locates a Files.com CLI binary.
- The Node file helper downloads a caller-supplied URL to a caller-supplied destination as part of file download functionality.
- API redirects remove Files.com authentication headers when the destination origin changes.
Evidence against
- The unusually large AutomationLog.js file contains generated AutomationLog model getters and appears related to the SDK's API models.
- Network and filesystem operations are present, but the inspected code uses them for SDK requests and caller-requested file downloads.
Behavioral surface
FilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
6 flaggedbuild.shView file
•path = build.sh
kind = build_helper
sizeBytes = 277
magicHex = [redacted]
Medium
lib/models/AutomationLog.jsView file
•path = lib/models/AutomationLog.js
kind = oversized_source_file
sizeBytes = 4629142
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
lib/models/AutomationLog.jsView on unpkgbin/files-cli-aiView file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
Findings
1 Critical2 High4 Medium5 Low
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limitedbin/files-cli-ai
HighPrevious Version Dangerous Deltalib/isomorphic/File.node.js
MediumNetwork
MediumShips Build Helperbuild.sh
MediumOversized Source Filelib/models/AutomationLog.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to files.com@1.2.779.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.779 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.