Check security reporting readiness for Claid AI repositories
Make private vulnerability reporting status easier to review for a repository connected to your 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
Repository security settings can go unchecked while teams focus on shipping image features.
- Checks whether private vulnerability reporting is enabled for a specified repository
- Builds a lightweight recurring security review habit
- Reports the result without repeated manual navigation
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 specified GitHub repository and summarize whether it is enabled.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real repository and confirm the result reflects its GitHub setting.
Questions about this workflow
Does the action enable private vulnerability reporting?
No. The listed action checks the repository's status; it does not change the setting.
Can this check every repository in an organization?
The listed action checks a specified repository. Name the repository to review in your instruction.
Does Claid AI provide the schedule?
No. Choose a recurring Notis schedule because Claid AI has no listed trigger event for this package.
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.