files.com@1.2.770
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest contains no install hook, the CLI wrapper only locates and runs an existing CLI when invoked, and the changed runtime code implements explicit SDK operations. The inspected API redirect logic also removes credentials when redirects leave the Files.com origin or protocol.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The SDK makes API requests or transfers files when its methods are called; the CLI wrapper runs when a user invokes it.
Impact
No malicious impact identified.
Mechanism
The SDK targets Files.com and exposes explicit file and restore operations. No automatic credential collection or unrelated network behavior was found.
AI rationale
The manifest contains no install hook, the CLI wrapper only locates and runs an existing CLI when invoked, and the changed runtime code implements explicit SDK operations. The inspected API redirect logic also removes credentials when redirects leave the Files.com origin or protocol.
Network endpoints1
app.files.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the Files.com SDK and declares build, test, lint, and watch scripts, with no install lifecycle script.
- The CLI shell wrapper locates and execs an existing files-cli binary when the command is run; it contains no install or import-time action.
- File.node.js provides URL download and filesystem stream helpers consistent with the SDK’s file-transfer purpose.
- The API client removes Files.com credentials on cross-origin redirects and strips sensitive authorization headers when the destination changes domain or protocol.
- Restore creation is an explicit SDK method that sends a POST to the Files.com restore endpoint.
Evidence against
- The package uses filesystem and network APIs, but the inspected uses support file transfer and API requests.
- The routing hints flag manifest differences and a changed file, but the inspected manifest, CLI wrapper, and runtime code show no concrete attack behavior.
Behavioral surface
FilesystemNetwork
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.770.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.770 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.