files.com@1.2.769
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source matches a Files.com API SDK: credentials are applied to explicit service requests, and the added Node helper performs caller-requested URL downloads. The manifest has no install lifecycle hooks, and the CLI shim only launches the CLI when invoked.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Network requests occur when SDK API methods are called; file transfers occur when their helper methods are called; the CLI shim runs when explicitly invoked.
Impact
Expected SDK API access and requested file transfers. No automatic credential disclosure or other malicious behavior was found.
Mechanism
The SDK sends configured Files.com API credentials in service-specific headers. Node helpers transfer a supplied URL to a supplied file or stream. The CLI shim locates and launches files-cli.
AI rationale
The source matches a Files.com API SDK: credentials are applied to explicit service requests, and the added Node helper performs caller-requested URL downloads. The manifest has no install lifecycle hooks, and the CLI shim only launches the CLI when invoked.
Evidence
caller-supplied destinationPath
Network endpoints1
app.files.com
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies this as the Files.com JavaScript SDK.
- SDK API requests use configured API keys or session IDs in Files.com-specific headers; authentication is added when sendRequest is called.
- The SDK defaults its API base URL to https://app.files.com.
- The Node file helper downloads a supplied URL to a supplied destination path when called.
- The CLI shim forwards arguments to a files-cli binary and reports an error if none is found.
Evidence against
- The manifest declares no install, preinstall, or postinstall lifecycle script.
- The inspected entry-point configuration and helper behavior show no automatic credential collection or unrelated network contact.
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
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to files.com@1.2.769.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.769 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.