files.com@1.2.752
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package shows no automatic malicious behavior, but its included build helper deletes npm and Yarn configuration files when run. This is a real destructive side effect without an explicit prompt, so warn rather than block.
Decision evidence
public snapshot- build.sh deletes ~/.npmrc and ~/.yarnrc before running the build; invoking it can remove the user's package-manager configuration.
- The manifest points to the SDK entry point and lists only build, test, lint, and watch scripts; it declares no install lifecycle script.
- SDK requests use the configurable Files.com base URL and the API key set by the caller.
- The build helper is not invoked by the manifest's scripts, so its deletions do not occur during normal package installation or import.
- The CLI wrapper only forwards arguments to an explicitly supplied or found files-cli binary.
- The SDK's default service endpoint is app.files.com.
Source & flagged code
6 flaggedbuild.sh deletes ~/.npmrc and ~/.yarnrc before running the build; invoking it can remove the user's package-manager configuration.
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.752.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.752 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.