@tachybase/module-cloud-component@1.6.46
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hooks, and the inspected runtime behavior supports the package’s cloud-component feature: it loads enabled server libraries after startup. The scanner’s shell-command indicator is a shell-language built-in keyword list in the client bundle, not a download-and-run operation.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and no runtime dependencies.
- The package entry point exports the server plugin.
- After startup, the plugin compiles and loads enabled cloud libraries marked for server use; this matches the package’s cloud-component purpose.
- The client bundle’s shell-command indicator is part of a `built_in` command-name list, not a shell execution call.
- Enabled library code runs in a VM context and receives a `require` function, so configured libraries can perform server-side actions.
- Enabled remote libraries can be fetched using authentication values configured for their source URL.
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.46.
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.46 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.