Check private vulnerability reporting on monitored GitHub repositories
Send repository references from Apify to Notis and check GitHub's private vulnerability reporting status.
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
Repository reviews can overlook whether a private channel exists for reporting vulnerabilities.
- Include reporting status in repository review follow-up.
- Spot repositories that may need a security settings review.
- Reduce manual checks across monitored repositories.
Setup
Build it in a few focused steps.
- 1Connect Apify and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for the repository security review.
- 3Tell Notis to take repository references from the incoming Apify result, check private vulnerability reporting status, and summarize the results.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real repository result and review the status summary.
Questions about this workflow
Does this workflow enable private vulnerability reporting?
No. The selected action checks its status; it does not change repository settings.
What must the Apify result contain?
It needs to identify the GitHub repository to check.
Can this check every repository in a large collection?
Notis can analyze returned data, but the result needs to provide the repositories to check and the workflow should summarize any limits or failures.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apify to GitHub. A trigger fires from one place; an action lands in another.
Apify 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.
Apify 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.