files.com@1.2.733
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package's main SDK behavior appears consistent with its Files.com purpose, but build.sh has an unexplained destructive side effect that can erase user package-manager configuration. Since the script is only manually invoked and is not wired into install or the declared build script, this warrants a warning rather than a publish block.
Decision evidence
public snapshot- build.sh silently deletes ~/.npmrc and ~/.yarnrc before running npm install and the build.
- The manifest has no install lifecycle hook, and build.sh is not among its declared npm scripts.
- The package identifies itself as the Files.com JavaScript SDK and uses app.files.com as its default API host.
- The CLI shim only delegates to a configured or package-local files-cli executable.
Source & flagged code
6 flaggedbuild.sh silently deletes ~/.npmrc and ~/.yarnrc before running npm install and the build.
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.733.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.733 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.