files.com@1.2.738
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThis is a real destructive risk in a manually invoked helper, so warn users before publishing. The package manifest does not run that helper on install, and the SDK's reviewed credential handling is tied to Files.com API requests.
Decision evidence
public snapshot- Running the shipped build.sh deletes ~/.npmrc and ~/.yarnrc before installing dependencies and building.
- package.json declares no install lifecycle hook, and its npm scripts do not invoke build.sh.
- The SDK uses a caller-provided Files.com API key for non-external requests; no unrelated credential flow was identified.
- The CLI wrapper delegates to an existing files-cli binary and does not download or execute code itself.
Source & flagged code
5 flaggedRunning the shipped build.sh deletes ~/.npmrc and ~/.yarnrc before installing dependencies and building.
build.shView on unpkg · L1Package 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.738.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.738 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.