@tachybase/module-cloud-component@1.6.41
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no install lifecycle scripts or runtime dependencies, and the flagged dynamic execution is tied to enabled cloud libraries. Remote fetching is conditional on library configuration and serves the package’s stated cloud component functionality; no unrelated attack behavior was identified.
Decision evidence
public snapshot- The manifest points to dist/server/index.js and declares no runtime dependencies.
- Remote library fetching is conditional on a library being configured with remote source, URL, and type; fetched content is cached.
- Server library compilation and loading run after application startup as part of the cloud library feature.
- Library code runs in a VM context with selected globals disabled, consistent with the package’s configurable cloud library feature.
- Enabled remote libraries can cause configured code to be fetched and executed at application startup.
- The VM sandbox exposes a context-specific require function, so its isolation is not a complete 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.41.
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.41 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.