@tachybase/module-cloud-component@1.6.49
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package’s remote-code feature is consistent with its purpose, and remote libraries are disabled by default. However, its CDN redirect handling forwards configured credentials to a potentially different host, a real credential-disclosure risk that merits a warning.
Decision evidence
public snapshot- At startup, the service loads enabled server-side cloud libraries and fetches uncached remote code using the library’s configured authentication.
- The CDN fetcher adds configured bearer or basic credentials to the request and passes those same credentials when following a redirect.
- The package describes itself as a cloud component module, and its library service supports fetching configured remote code.
- Cloud libraries default to disabled, so this behavior requires an enabled library configuration.
- No hard-coded external destination or install lifecycle script was identified; the code URL and credentials come from the library configuration.
Source & flagged code
6 flaggedPackage source executes code through a VM context API.
dist/server/services/cloud-libraries-service.jsView on unpkg · L47At startup, the service loads enabled server-side cloud libraries and fetches uncached remote code using the library’s configured authentication.
dist/server/services/cloud-libraries-service.jsView on unpkg · L200Findings
Affected versions and remediation
This report applies to @tachybase/module-cloud-component@1.6.49.
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.49 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.