files.com@1.2.730
Files.com SDK for JavaScript
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest contains no lifecycle hook, and the SDK’s network path is consistent with its Files.com service purpose. The build helper removes npm and Yarn configuration only when manually run; the package does not invoke it during installation or import.
Decision evidence
public snapshot- The manifest has no install, preinstall, or postinstall hook; its scripts are build, test, lint, and watch.
- The SDK defaults to app.files.com and sends its API key or session ID only on non-external API requests.
- The CLI wrapper forwards arguments to an existing files-cli binary when the command is run; it does not download or execute code during installation.
- The oversized AutomationLog file’s readable source defines ordinary SDK model fields and methods.
- build.sh removes ~/.npmrc and ~/.yarnrc when manually run, but the manifest does not invoke it as an install hook.
Source & flagged code
6 flaggedPackage 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.730.
See all versions of files.com for other recorded verdicts.
- Review the evidence and your use of files.com@1.2.730 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.