@tachybase/module-cloud-component@1.6.62
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no lifecycle scripts, and its server entry loads application-configured cloud libraries rather than running an install-time payload. VM evaluation and remote synchronization are consistent with the package’s cloud-component purpose; the inspected client sync flow is user-triggered.
Decision evidence
public snapshot- The manifest has no lifecycle scripts or runtime dependencies; its main entry is dist/server/index.js.
- Server code loads only enabled server cloud-library records from the application database and runs their stored code in a VM context.
- Remote library code is fetched only when a library is configured with a remote source and URL; the client exposes an explicit sync action.
- The package’s purpose is to provide cloud components and libraries, so compiling and loading configured library code matches its function.
- The VM code is not executed as a package install hook; it runs as part of the application’s cloud-library loading feature.
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.62.
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.62 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.