Verify private vulnerability reporting for sensitive projects
Confirm the right security reporting path before sensitive work begins.
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
Security settings are often checked too late, after a project already contains sensitive details.
- Catch security gaps early
- Create a repeatable handoff
- Reduce risky project setup
Setup
Build it in a few focused steps.
- 1Connect Check Cherry and GitHub once in Notis.
- 2Create an automation named Sensitive project security check.
- 3Tell Notis to check private vulnerability reporting for the linked repository after a sensitive project webhook.
- 4Choose the webhook trigger and a report channel.
- 5Test with one real handoff.
Questions about this workflow
What if reporting is disabled?
Ask Notis to report the repository and recommended follow up for manual remediation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Check Cherry to GitHub. A trigger fires from one place; an action lands in another.
Check Cherry 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.
Check Cherry 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.