@tachybase/module-cloud-component@1.6.42
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hooks, and the server’s remote fetching and VM execution are tied to configured cloud libraries, which matches the package’s purpose. The inspected source does not show unrelated data collection or other malicious behavior.
Decision evidence
public snapshot- The manifest has no lifecycle scripts, and its main entry is the server plugin.
- Remote code is fetched only when a library is configured with remote source, URL, and code type; the service caches that code.
- The server loads enabled cloud libraries at startup and executes their code in a VM context with selected globals disabled, consistent with the package’s cloud component purpose.
- Enabled server libraries are compiled and executed automatically after startup; this is a consequential capability, but it is part of the package’s stated cloud component function.
Source & flagged code
5 flaggedPackage source executes code through a VM context API.
dist/server/services/cloud-libraries-service.jsView on unpkg · L47Package contains source files above the normal full-analysis size ceiling.
dist/client/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @tachybase/module-cloud-component@1.6.42.
See all versions of @tachybase/module-cloud-component for other recorded verdicts.
- Review the evidence and your use of @tachybase/module-cloud-component@1.6.42 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.