@goldskycom/cli@13.13.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 high-risk primitives are package-aligned, user-invoked CLI functionality rather than automatic or covert behavior. The manifest has no install lifecycle hook, and inspection found no malicious credential or payload flow.
Decision evidence
public snapshot- The CLI can invoke a remote Turbo installer only after the user runs the Turbo command and accepts its prompt.
- The Compose installer is reached only through the explicit `goldsky compose install` subcommand.
- The manifest exposes a CLI entry point and contains no npm install lifecycle hook.
- No install-time execution, self-dependency, credential harvesting, or covert exfiltration was found.
- The flagged eval and Function uses are bundled dependency internals, not a flow that fetches and executes a hidden payload.
- Telemetry removes authentication before sending and redacts the token option from recorded commands.
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 · L1815Findings
Affected versions and remediation
This report applies to @goldskycom/cli@13.13.0.
See all versions of @goldskycom/cli for other recorded verdicts.
- Review the evidence and your use of @goldskycom/cli@13.13.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.