@tachybase/module-cloud-component@1.6.66
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no install hooks, and its network fetching and server-side code execution are part of its configurable cloud-library feature. Libraries are disabled by default and only enabled records are compiled and loaded.
Decision evidence
public snapshot- The package has no install or lifecycle scripts.
- Cloud libraries are disabled by default, and compilation selects only enabled records.
- Server libraries load after application startup; their code runs in a VM context.
- Remote code is fetched from each library's configured URL and path.
- Enabled server libraries execute automatically at startup, which is a powerful capability.
- The VM context exposes a require bridge; this supports the cloud-library feature but means configured library code is not isolated from application modules.
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.66.
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.66 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.