files.com@1.2.732
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe SDK’s network behavior fits its Files.com API purpose, but build.sh removes user package manager configuration as a side effect of building. This is a real data loss risk, though it is not triggered automatically.
Decision evidence
public snapshot- Running build.sh deletes ~/.npmrc and ~/.yarnrc before installing dependencies and building.
- The manifest lists build, test, lint, and watch scripts, with no install lifecycle script that invokes build.sh.
- The SDK’s default service endpoint is https://app.files.com, consistent with the package’s Files.com API purpose.
- The flagged AutomationLog model exposes an API list method; its large size comes from generated filter documentation.
Source & flagged code
6 flaggedRunning 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.732.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.732 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.