files.com@1.2.740
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiNo install-time or import-time attack was identified, and the SDK routes credentials with requests to its configured Files.com service. The shipped build helper nevertheless deletes user package-manager configuration when invoked, so warn about that destructive behavior.
Decision evidence
public snapshot- The package exposes an SDK entry point and a CLI shim; its manifest declares no install lifecycle scripts.
- The API client sends session or API-key credentials only on non-external requests, and its default base URL is app.files.com.
- The shipped build.sh removes ~/.npmrc and ~/.yarnrc before building, which can delete the user’s npm and Yarn configuration when the helper is run.
- The npm build script runs Babel directly and does not invoke build.sh.
- The CLI shim locates an existing files-cli binary and executes it; it does not download or install one.
Source & flagged code
6 flaggedPackage contains source files above the normal full-analysis size ceiling.
lib/models/AutomationLog.jsView on unpkgFindings
Affected versions and remediation
This report applies to files.com@1.2.740.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.740 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.