Operations · Intermediate
Triage package vulnerabilities and manage quarantine policies
Review artifact vulnerability scans, assess dependency exposure, and quarantine high-risk packages
Use with BotBento Markdownالعربية
Opens BotBento. Paste the prompt into a bot; nothing is preconfigured.
- When something happensVulnerability scan completed
- ThenEvaluate dependency blast radius
- ResultSeek sign-off to quarantine package
When dependency scanners flag Common Vulnerabilities and Exposures in published build packages or cached third-party libraries, this bot parses the scan reports, maps exposure across repositories, and drafts quarantine recommendations. It alerts maintainers and prepares registry policy updates to prevent compromised packages from breaking downstream production builds.
Prompt to start with
BotBentoRecommended
Inspect incoming vulnerability scan outputs from the package registry and container scanners. When critical or high severity CVEs appear, query the database to identify which services rely on the flagged package version. Prepare a summary of affected repositories, available patched versions, and a draft command to quarantine the artifact in the registry. Present this analysis in Slack, and await explicit operator approval before modifying registry access policies, isolating packages, or creating security advisory tickets in GitHub.