@tachybase/module-cloud-component@1.6.43
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged VM execution is part of a cloud-component service: it compiles and loads enabled library records during application startup. No lifecycle script or unrelated collection behavior was found, so this version is clean.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and points its main entry to the server plugin.
- The service compiles only cloud libraries marked enabled.
- Server libraries are loaded at application startup from configured effect-library records.
- The VM execution applies to configured library code; no unrelated collection or external destination is identified.
- The package supports executing custom cloud-library code, including code fetched from a configured remote URL; this is a broad capability intrinsic to its 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.43.
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.43 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.