Add vulnerability reporting status to repository reviews
Keep a security setting in view while your team maintains the code behind image workflows.
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
A security reporting setting can be overlooked when repository reviews focus only on code changes and pull requests.
- Provides a recurring view of one repository's reporting status
- Separates a security setting review from delivery work
- Summarizes whether the feature is enabled
Setup
Build it in a few focused steps.
- 1Connect Claid AI and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to check private vulnerability reporting for the named image workflow repository and report whether it is enabled.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real repository and verify the reported setting.
Questions about this workflow
Does Notis turn the setting on?
No. The listed action only checks private vulnerability reporting status.
Can I check more than one repository?
This action is described for a specified repository. Create separate checks or provide a clear list only if the workflow can handle each named repository in context.
Why use a recurring schedule?
A schedule gives you a regular reminder of the status without requiring a Claid AI trigger event, which is not available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Claid ai to GitHub. A trigger fires from one place; an action lands in another.
Claid ai 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.
Claid ai 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.