@tachybase/module-cloud-component@1.6.40
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe VM execution and network requests belong to the package’s cloud-library feature: enabled library code is loaded at application startup, and remote fetching depends on per-library configuration. The manifest has no lifecycle scripts or runtime dependencies, and the inspected code does not show an unrelated endpoint or automatic credential collection.
Decision evidence
public snapshot- The manifest has no runtime dependencies or lifecycle scripts, and its main entry is the server plugin.
- The service loads enabled cloud libraries and fetches remote code only when a library is configured with a remote source, URL, and type.
- Server code is compiled and executed by the cloud-library loader as part of that feature.
- The controller compiles code supplied through cloud-library update or publish actions.
- Remote fetching uses a URL and optional credentials provided to the fetcher; the source shows no fixed external collector.
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.40.
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.40 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.