files.com@1.2.748
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe declared install and npm scripts do not trigger the destructive helpers, and the SDK routes configured credentials to its Files.com API. However, manually running either build.sh or test.sh deletes ~/.npmrc and ~/.yarnrc without explaining that side effect, so warn about this destructive capability.
Decision evidence
public snapshot- build.sh deletes ~/.npmrc and ~/.yarnrc before building.
- test.sh also deletes ~/.npmrc and ~/.yarnrc before installing dependencies.
- The declared npm scripts run Babel, Jest, or ESLint and do not invoke these shell helpers.
- The SDK attaches configured credentials to its own relative API requests.
- The manifest declares no install lifecycle scripts.
- The CLI wrapper locates and runs files-cli; it does not collect credentials or contact a host itself.
Source & flagged code
6 flaggedbuild.sh deletes ~/.npmrc and ~/.yarnrc before 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.748.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.748 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.