GitHub
Leak events are turned into GitHub issues.
How it works
The connection uses a fine-grained access token. The token is limited to one repository and one permission: read and write issues.
Three labels are added: darkradar, the severity, and one specific to the event. The last one prevents duplicates; when the same leak returns, no new issue is opened and a comment is added to the existing one.
Those running GitHub Enterprise on their own server also supply the API address; it has to be https.
Limits
Writes go only to the named repository.
Issues are not closed or deleted, and the code is not touched.
The leaked value itself is not written to the issue.
Setup
The setup steps are in the panel, on the integration’s own screen. What to do on the provider side and which value goes where is written there.