sentry-cli
Pass
Audited by Gen Agent Trust Hub on Nov 9, 2026
Risk Level: SAFE
Full Analysis
- [REMOTE_CODE_EXECUTION]: The skill's installation instructions utilize a common developer pattern where a script is fetched from an official vendor domain and piped directly to a shell for execution.
- Evidence:
curl https://cli.sentry.dev/install -fsS | bashinSKILL.md. - Context: The download targets the official Sentry CLI installation domain managed by the vendor. This is a standard and expected installation method for this tool.
- [COMMAND_EXECUTION]: The skill facilitates the execution of the
sentryCLI and common auxiliary utilities to process data and manage projects. - Evidence: Frequent use of
sentrycommands, as well asjqfor JSON processing andgitfor repository metadata. - Context: These operations are necessary for the primary purpose of the skill, which is to provide a command-line interface for Sentry.
- [DATA_EXPOSURE]: The skill instructs the agent on how the CLI automatically detects configuration and credentials from local project files.
- Evidence: Documentation describes the CLI scanning for
.sentryclircand.envfiles to resolve authentication and project settings. - Context: This is standard behavior for the Sentry CLI to provide seamless integration with existing project configurations and is not indicative of malicious data harvesting.
- [PRIVILEGE_ESCALATION]: The command reference includes an example for repairing the CLI's local database that involves elevated permissions.
- Evidence:
sudo sentry cli fixinreferences/cli.md. - Context: This is documented as a diagnostic and repair step for fixing file ownership issues in the tool's local configuration directory, provided as a troubleshooting option for the user.
Audit Metadata