files.com@2.0.7
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest and entry points show no install-time behavior, while API credentials are used for configured Files.com requests with cross-origin redirects blocked. The scanner’s manifest and semantic-analysis warnings were not supported by the inspected source.
Static reason
No blocking static signals were detected.
Trigger
SDK requests occur when callers invoke API methods; the CLI wrapper runs when a user invokes files-cli-ai.
Impact
No malicious impact identified; normal API and CLI behavior is consistent with the package purpose.
Mechanism
API credentials are supplied through SDK configuration and sent with requests to the configured Files.com service. Redirects are handled manually to prevent credentials crossing origins.
AI rationale
The manifest and entry points show no install-time behavior, while API credentials are used for configured Files.com requests with cross-origin redirects blocked. The scanner’s manifest and semantic-analysis warnings were not supported by the inspected source.
Network endpoints1
app.files.com
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest lists only build, test, lint, and watch scripts; it declares no install lifecycle script.
- The package entry point only exports the SDK’s Attachment, Files, and Logger modules.
- The SDK defaults API requests to https://app.files.com and requires a configured API key or session before adding its credential to a request.
- The SDK handles redirects itself so credentials do not cross to another origin.
Evidence against
- The package exposes an AI CLI wrapper, but it runs only when invoked and delegates to an explicitly configured or discovered files-cli binary.
- No automatic install-time collection, unrelated endpoint, or credential exfiltration was identified.
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
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to files.com@2.0.7.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@2.0.7 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.