files.com
Files.com SDK for JavaScript
This report shows the evidence for files.com@1.2.742. 1 of 97 known versions is blocked or flagged. The newest version, 2.0.24, is allowed. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe standalone build and test helpers silently delete the user's npm and Yarn configuration files, an unrelated destructive action that can remove settings and credentials. The behavior is not wired to package installation, but it makes the package malicious when those helpers are run.
Decision evidence
public snapshot- build.sh deletes ~/.npmrc and ~/.yarnrc before installing dependencies and building.
- test.sh also deletes ~/.npmrc and ~/.yarnrc before installing dependencies and running tests.
- package.json defines no install, preinstall, or postinstall lifecycle hook; its npm scripts run build, test, lint, or watch.
- The main SDK entry initializes Files.com API configuration; requests use the Files.com service and require an API key.
Source & flagged code
6 flaggedbuild.sh deletes ~/.npmrc and ~/.yarnrc before installing dependencies and building.
build.shView on unpkg · L3Package 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.742.
The versions list below shows the verdict for each recorded version.
- Avoid installing files.com@1.2.742. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.