files.com@2.0.23
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package manifest and inspected entry points match a Files.com SDK and CLI wrapper: there are no install hooks, and the SDK's default endpoint is its own service. The scanner's manifest and semantic-analysis flags did not correspond to attack behavior in the inspected files.
Static reason
No blocking static signals were detected.
Trigger
Library requests occur when an application uses the SDK; the CLI wrapper runs only when invoked.
Impact
No automatic collection, unrelated network contact, or harmful account action was identified.
Mechanism
The SDK sends API requests to its configured Files.com base URL. The wrapper locates and launches an existing CLI binary.
AI rationale
The package manifest and inspected entry points match a Files.com SDK and CLI wrapper: there are no install hooks, and the SDK's default endpoint is its own service. The scanner's manifest and semantic-analysis flags did not correspond to attack behavior in the inspected files.
Network endpoints1
app.files.com
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 identifies this as the Files.com JavaScript SDK and declares lib/Files.js as its main entry point.
- The package declares build, test, type-check, lint, and watch scripts; it has no install lifecycle script.
- The SDK defaults API requests to https://app.files.com and leaves its API key unset until configured.
- The AI CLI wrapper launches an existing files-cli binary when invoked; it does not download or install one.
- The changed File model code manages model attributes returned by its constructor or server.
Evidence against
- The CLI wrapper can execute a binary found at /usr/local/go/bin/files-cli or at package-relative paths when the command is run.
- build.sh runs npm install and the build command when manually invoked.
Behavioral surface
CryptoEnvironmentVarsFilesystemNativeBindingsNetwork
HighEntropyStringsMinifiedUrlStrings
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
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to files.com@2.0.23.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@2.0.23 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.