files.com@2.0.13
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected entry points and network code match the Files.com SDK purpose: requests default to Files.com, and the CLI shim only dispatches to a configured or local executable. The scanner’s registry manifest discrepancy was not independently verifiable from the package source.
Static reason
No blocking static signals were detected.
Trigger
SDK API calls or explicit invocation of files-cli-ai; no install hook runs automatically.
Impact
No unauthorized credential collection, unrelated network contact, account action, or destructive behavior was identified.
Mechanism
The SDK sends configured credentials in Files.com API requests. The CLI wrapper selects an explicitly configured binary or checks local paths, then exits if none is found.
AI rationale
The inspected entry points and network code match the Files.com SDK purpose: requests default to Files.com, and the CLI shim only dispatches to a configured or local executable. The scanner’s registry manifest discrepancy was not independently verifiable from the package source.
Network endpoints2
app.files.comHTTPS subdomains of files.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json uses lib/Files.js as the main entry and declares no install lifecycle hooks.
- The npm scripts are build, test, test:types, lint and watch; none is an install hook.
- The AI CLI shim runs only a configured FILES_CLI_BINARY or a local files-cli executable.
- The SDK defaults to https://app.files.com and uses its configured API key in the Files.com API key header.
- Region-mismatch hosts are restricted to HTTPS origins; the source identifies Files.com and its subdomains as the hosts that may receive credentials automatically.
- The NODE_OPTIONS reference checks whether to avoid starting a download worker; it does not transmit the environment value.
Evidence against
- The scanner reported a manifest difference from the registry, but that difference could not be independently verified from the package source available for review.
Behavioral surface
CryptoEnvironmentVarsFilesystemNativeBindingsNetwork
Source & flagged code
5 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 = 4631391
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 Critical1 High5 Medium5 Low
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limitedbin/files-cli-ai
MediumNetwork
MediumEnvironment Vars
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@2.0.13.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@2.0.13 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.