@goldskycom/cli@13.10.0
The Goldsky CLI to deploy subgraphs, index & transform blockchain data, configure webhooks, and access your data in real-time.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a user-confirmed remote installer that pipes a Goldsky-hosted script into a shell. The scanner's claims of credential redirection and foreign-package overwrite were not supported by the inspected source.
Decision evidence
public snapshot- The turbo command downloads and executes a script from a Goldsky host through a shell.
- The remote installation occurs after an interactive confirmation.
- The installed executable is placed under the user's Goldsky directory.
- package.json has no preinstall, install, or postinstall hook.
- The package entrypoint is a user-invoked CLI binary.
- The shell installation path is limited to the explicit turbo command and Goldsky-owned host.
- No source evidence shows credential harvesting, foreign package overwrite, or agent-control changes.
Source & flagged code
13 flaggedSource fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
dist/index.jsView on unpkg · L1740Findings
Affected versions and remediation
This report applies to @goldskycom/cli@13.10.0.
See all versions of @goldskycom/cli for other recorded verdicts.
- Review the evidence and your use of @goldskycom/cli@13.10.0 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.