@tachybase/module-cloud-component@1.6.65
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no install hooks, and the flagged VM and network behavior implement its cloud library feature. Server code execution is limited to enabled server libraries, while remote fetching uses a configured URL; no unrelated collection or attack behavior was found.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and declares no runtime dependencies.
- Server libraries are selected only when enabled and marked for server use.
- Library compilation and loading run after application startup as part of the cloud component feature.
- Remote code fetching takes a configured URL and optional authentication parameters.
- The package intentionally executes configured server library code in a VM context; its require function can resolve Node modules, so this is not a security boundary.
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.65.
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.65 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.