On a schedule
Get Slack alerts for risky dependencies
Each day Slack lists new security alerts for packages and GitHub Actions used in your repositories, most severe first.
- Runs
- On a schedule
- Apps
- GitHub, Slack
- AI
- Optional
- Access
- Dependabot alerts read, contents read; chat:write
Send this to your assistant
Create a ClickRuntime automation: every morning, check Dependabot alerts across our GitHub repos and post any new high or critical ones to #security, with the package, repo and fix version.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A web agency maintains thirty client repositories. Dependabot raises security alerts in each one, but nobody watches thirty alert tabs, so a critical vulnerability in a popular package can sit unnoticed for weeks.
Collecting new alerts from every repository into one Slack message each morning makes them impossible to miss. The team sees the most severe first and knows exactly which repository and version to update.
What you get out of it
One place for every repository
Alerts from all repositories arrive in a single message. Nobody needs to check each repository's security tab.
Most severe first
Critical and high alerts lead the list. The team fixes what matters most before the rest.
Each alert is reported once
Alerts already posted are remembered, so the message only contains news. The channel stays readable.
The fix is in the message
Each line shows the package, the affected repository and the version that fixes it. Acting on it is a quick update, not research.
How it works
What happens, step by step
Every morning, ClickRuntime reads open Dependabot security alerts from your GitHub organisation.
It keeps alerts at the severity you choose and skips any it has already posted.
If you turn on AI, it adds a plain explanation of the most serious ones.
New alerts are posted to your #security Slack channel, most severe first, with the repository and fixed version.
Before it runs live
- Connect GitHub
- Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Google Sheets
- Combine it with other GitHub and Slack steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http, notify, state, ai
def gh(method, path, **kw):
resp = http.request(method, f"https://api.github.com{path}", headers={
"Authorization": f"Bearer {credentials.connection('github', 'work')}", "Accept": "application/vnd.github+json"}, **kw)
return resp.raise_for_status() or (resp.json() if resp.content else None)
ORG, LEVELS = "acme", ("critical", "high")
ORDER = {"critical": 0, "high": 1, "medium": 2, "low": 3}
@on_trigger
def run(event):
alerts = gh("GET", f"/orgs/{ORG}/dependabot/alerts", params={"state": "open", "severity": ",".join(LEVELS), "per_page": 100})
seen = set(state.get("seen") or [])
new = sorted((a for a in alerts if a["html_url"] not in seen), key=lambda a: ORDER[a["security_advisory"]["severity"]])
if not new:
return {"new": 0}
lines = [f"[{a['security_advisory']['severity']}] {a['dependency']['package']['name']} in {a['repository']['name']}: "
f"{a['security_advisory']['summary']} (fixed in {(a['security_vulnerability'].get('first_patched_version') or {}).get('identifier', 'no fix yet')})"
for a in new]
text = f"{len(new)} new dependency alerts\n" + "\n".join(lines)
try:
text += "\n\n" + ai.generate("\n".join(lines[:5]), system="In two plain sentences, explain the biggest risk here.", max_output_tokens=120).text
except (ai.AINotIncluded, ai.AILimitReached):
pass
notify.slack(text, channel="#security")
state.set("seen", sorted(seen | {a["html_url"] for a in new}))
return {"new": len(new)}FAQ
Common questions
Do I need Dependabot turned on?
Can it include medium and low alerts?
What does AI add?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Post a daily engineering digest from GitHub in Slack
Each morning before standup, Slack shows what merged yesterday, which pull requests are waiting for review and which issues were opened.
See how it worksBack up exports to GitHub each night
Every night your configuration or workflow exports are saved to a GitHub repository, and Slack lists exactly what changed.
See how it worksTrack flaky CI jobs in GitHub Actions
Each morning Slack lists the GitHub Actions workflows that failed and then passed on a re-run in the last week, so you know which tests are flaky.
See how it worksKeep exploring
Set up “Get Slack alerts for risky dependencies” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.