files.com@2.0.9
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected manifest has no install lifecycle hook, and the CLI wrapper only forwards an explicit invocation to a files-cli binary. The SDK defaults to Files.com's service and uses credentials provided through its configuration or request options; no unrelated collection or harmful automatic behavior was identified.
Decision evidence
public snapshot- The manifest identifies this as the Files.com JavaScript SDK and points to lib/Files.js as its main entry point.
- The manifest's npm scripts are build and test commands; no lifecycle script is declared.
- The CLI wrapper launches files-cli only when the user invokes the command, and looks for local or configured binary paths.
- The SDK defaults to https://app.files.com and does not set an API key by default.
- API credentials are taken from explicit request options or SDK configuration, then used by the SDK request flow.
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.9.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@2.0.9 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.