DEVOPS
Publish a release CVE-readiness report on tag
When a release tag is cut, scans all images in the release, evaluates each against the severity budget.
How it runs
The automated pipeline, trigger to output.
- TriggerRelease tag createdGitHub
- ActionScan all images in the releaseGitHub
- LogicScore images and compute go/no-go
- ActionPublish readiness report to ConfluenceConfluence
- OutputPost verdict and link to SlackSlack
What it does
This workflow turns a release tag into an auditable security gate. On tag creation it scans every container image bundled in the release, scores each against your severity budget, and assembles a readiness report — per-image CVE counts, which images pass, and an overall go/no-go verdict. The report is published to Confluence and a short notice with the verdict and link is dropped in Slack.
When to use it
Use it for release sign-off when you need a durable, shareable record of the security posture at the moment of cutting a release — useful for compliance, change advisory boards, or simply giving release managers a single yes/no answer.
How it works
- 1A release tag creation event triggers the run.
- 2An action enumerates the images in the release and scans each for CVEs.
- 3A branch scores each image against the severity budget and computes a verdict.
- 4An action publishes the formatted readiness report to Confluence.
- 5A final step posts the go/no-go verdict and report link to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.