Check private reporting readiness from a security alert
Make the next security step clearer by checking whether the related repository accepts private vulnerability reports.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
Why this helps
A security alert can arrive before anyone remembers whether the repository has private reporting enabled.
- Make repository reporting readiness visible alongside a security alert.
- Reduce manual investigation before deciding how to handle a vulnerability.
- Keep the repository status in the alert's follow-up report.
Setup
Build it in a few focused steps.
- 1Connect Alchemy and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to check private vulnerability reporting for the repository identified by the incoming alert.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real alert and confirm the repository status is reported.
Questions about this workflow
Does this change the repository's vulnerability reporting setting?
No. It checks whether private vulnerability reporting is enabled.
What if the alert refers to a contract but not a repository?
The GitHub check needs a repository. Supply a way to identify it in your instruction or include that information in the webhook request.
Can this workflow file a security issue?
This workflow only checks the reporting setting. Its action is not an issue creation action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Alchemy to GitHub. A trigger fires from one place; an action lands in another.
Alchemy triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Alchemy and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.