@decoopus/claude-setup@1.0.4
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe inspected source implements an explicitly invoked gateway setup flow: it prompts for a gateway key, displays the endpoint, and stores those values in Claude Desktop configuration. The default is a publisher-selected third-party gateway, but the package does not transmit existing service credentials or perform hidden install-time actions.
Decision evidence
public snapshot- package.json exposes bin/cli.js as the command entrypoint and defines only a start script, with no install lifecycle hook.
- The CLI uses https://api-anthropic.help as its default gateway and displays the selected gateway endpoint in its setup summary.
- Setup prompts the user for a gateway API key and stops if the key is empty.
- The CLI saves the entered key as Claude Desktop's gateway key in configuration files when the user runs setup.
- The publisher-selected default gateway receives the entered key through Claude Desktop's saved gateway configuration, so later use depends on trusting that third-party service.
Source & flagged code
7 flagged · loading sourcepackage.json exposes bin/cli.js as the command entrypoint and defines only a start script, with no install lifecycle hook.
package.jsonView on unpkg · L5The CLI uses https://api-anthropic.help as its default gateway and displays the selected gateway endpoint in its setup summary.
bin/cli.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @decoopus/claude-setup@1.0.4.
See all versions of @decoopus/claude-setup for other recorded verdicts.
- Review the evidence and your use of @decoopus/claude-setup@1.0.4 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.