TraceClaw validates GitHub webhook signatures and deduplicates deliveries. Analysis APIs require GitHub sign-in and access to the repository. Production secrets belong exclusively on the server.
TraceClaw · updated October 20, 2026
Security and permissions
Requested permissions: Contents read-only for pull-request context; Metadata read-only as required by GitHub; Checks read/write to publish neutral analysis checks; Pull requests read/write to read diffs and publish inline findings. TraceClaw does not request organization administration or secrets access.
Select only the repositories you want analyzed. Telemetry configuration is currently managed by the operator on the server. The adapter matches an exact installation and repository binding before querying the configured service and environment. This code-level control does not replace operator verification of credential scope, monitored service and metrics. Keep telemetry disabled until those are confirmed.
Use the configured support contact to ask for a private reporting channel before sharing vulnerability details. If no contact is shown, private intake is not yet configured. Do not disclose exploit details, private code or credentials in a public issue. No certification, independent audit or GitHub Verified Publisher status is claimed.
Support contact is awaiting operator configuration.