files.com@1.2.725
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package behaves like a Files.com SDK: it has no install hook, uses its own service by default, and sends credentials only on non-external requests. The unusual build helper is not invoked by package lifecycle scripts and requires a user to run it directly.
Static reason
No blocking static signals were detected.
Trigger
SDK network requests follow consumer API calls; the CLI wrapper acts only when invoked.
Impact
No unauthorized collection, account action, or automatic code execution was identified. The separate build.sh helper deletes npm and Yarn config files only when manually run.
Mechanism
The SDK targets its configured service and omits Files.com credentials for external URLs. The CLI delegates to a configured or package-local binary.
AI rationale
The package behaves like a Files.com SDK: it has no install hook, uses its own service by default, and sends credentials only on non-external requests. The unusual build helper is not invoked by package lifecycle scripts and requires a user to run it directly.
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 points to the Files.com SDK entry point and declares no install lifecycle scripts.
- The package scripts are build, test, lint, and watch; none is an install hook.
- The CLI wrapper runs only when invoked and delegates to a configured or package-local files-cli binary.
- The SDK defaults to https://app.files.com and only attaches its API key or session ID to non-external requests.
- The changed PartnerChannel models expose explicit API operations that validate supplied parameters before sending requests.
Evidence against
- build.sh removes ~/.npmrc and ~/.yarnrc when manually run, but the package manifest does not invoke it during installation.
Behavioral surface
FilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Oversized source lightweight scan
Source & flagged code
6 flaggedbuild.shView file
•path = build.sh
kind = build_helper
sizeBytes = 102
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 Critical1 High4 Medium6 Low
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limitedbin/files-cli-ai
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
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to files.com@1.2.725.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.725 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.