@tachybase/module-cloud-component@1.6.64
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no lifecycle scripts, and the flagged VM execution is limited to enabled cloud libraries loaded by the host application. This behavior matches the package's cloud-component purpose; the client bundle's download/run hint did not establish shell execution.
Decision evidence
public snapshot- The manifest declares no lifecycle scripts.
- The service compiles only cloud libraries marked enabled.
- The service registers compilation and loading after the host application starts.
- Configured server library code runs in a VM context as part of the cloud-library feature.
- No package install hook or automatic network contact is present in the manifest.
- The reviewed execution path is for configured cloud libraries, matching the package's stated cloud-component purpose.
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.64.
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.64 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.