files.com@2.0.4
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe reviewed behavior matches a Files.com SDK: there is no install hook, API credentials come from client configuration, and requests target the configured service. The CLI wrapper only delegates an invoked command, and the build helper performs a conventional npm install and build.
Decision evidence
public snapshot- The manifest identifies this as the Files.com JavaScript SDK and points its main entry to lib/Files.js.
- The manifest has no install lifecycle hook; its scripts are for building, testing, linting, and watching.
- The SDK obtains credentials from caller or client configuration and adds them to API requests.
- The CLI wrapper forwards an explicitly invoked command to a configured or package-local files-cli executable.
- The API client sends requests to its configured service site and limits credential rerouting to an API response from that site.
Source & flagged code
5 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@2.0.4.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@2.0.4 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.