Review private vulnerability reporting settings
Keep a periodic view of whether private vulnerability reporting is enabled for the repositories you care about.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
Why this helps
Security settings can be overlooked when research and repository follow-up live in separate places.
- Review a defined set of repositories
- See which repositories have private reporting enabled
- Keep security follow-up in a run report
Setup
Build it in a few focused steps.
- 1Connect Clearout and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to check private vulnerability reporting status for each repository in the supplied Clearout research list and report results.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real repository from the list.
Questions about this workflow
Does this turn the setting on if it is disabled?
No. This GitHub action checks status only. It does not change repository settings.
What repositories will be checked?
Provide the repository names or a list in the automation prompt or scheduled input. Clearout has no listed trigger events.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clearout to GitHub. A trigger fires from one place; an action lands in another.
Clearout 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.
Clearout 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.