@tachybase/module-cloud-component@1.6.48
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hooks, and importing the package only exports its plugin. The flagged VM execution and network access are tied to configured cloud libraries and their URLs, consistent with the package's purpose; no attack behavior was found.
Decision evidence
public snapshot- The manifest has no install lifecycle scripts or runtime dependencies.
- The main entry exports the server plugin; importing it does not itself fetch or execute library code.
- Server code is compiled and loaded for enabled cloud libraries, with execution tied to the app's afterStart event.
- Remote code fetching uses a library's configured URL and optional configured credentials; no fixed external collector is identified.
- Enabled server cloud libraries execute code from the database at application startup, and the VM sandbox exposes a require function; this is a broad capability, but it serves the package's cloud-library feature.
- The package fetches configured remote code and caches it for enabled libraries.
Source & flagged code
6 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.48.
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.48 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.