Check repository reporting readiness during security reviews
Use public security signals to focus a recurring check of private vulnerability reporting for the repositories you specify.
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 review details are spread across public sources and repository settings, making it easy to miss a readiness gap.
- Pair external signals with a repository setting check
- Keep security review steps on a predictable schedule
- Identify repositories that may need a settings follow-up
Setup
Build it in a few focused steps.
- 1Connect Bright Data MCP and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the security review.
- 3Tell Notis which public security sources and GitHub repositories to review, and to report private vulnerability reporting status for each repository.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real public source and a repository you can access.
Questions about this workflow
Does this change repository security settings?
No. The selected GitHub event checks private vulnerability reporting status; it does not enable or change the setting.
What if the research source does not name a repository?
Tell Notis which repositories to check independently. Do not rely on Bright Data to supply repository names unless the source actually contains them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bright Data MCP to GitHub. A trigger fires from one place; an action lands in another.
Bright Data MCP 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.
Bright Data MCP 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.