@tachybase/module-cloud-component@1.6.67
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package is not clearly malicious, but its remote-code fetcher forwards configured authentication credentials across redirects without validating the destination host. This is a concrete credential-handling risk, although it requires a remote library configuration and a redirect response.
Decision evidence
public snapshot- The fetcher adds a configured bearer token to the Authorization header.
- On an HTTP redirect, the fetcher follows the redirect by calling itself with the same authentication arguments; it does not check that the destination host matches the configured URL.
- The remote fetch path is used only for cloud libraries configured with a remote source and URL.
- The manifest has no install lifecycle scripts and declares no runtime dependencies.
- The package’s remote-code feature is explicitly configured with a source URL and authentication settings.
- The VM execution occurs in the cloud-library loading feature, which runs after the application starts and handles enabled libraries.
- No hard-coded external collector or unrelated destination was identified.
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.67.
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.67 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.