Repository navigation
Release notes: Vibgrate CLI 2026.1020.1 — fail CI on exploit likelihood with --fail-on-epss #490
vibgrate-team
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What's new in 2026.1020.1
Shipped 20 Oct 2026. Full release: https://github.com/vibgrate/cli/releases/tag/v2026.1020.1 · Changelog: https://vibgrate.com/changelog/cli/2026.1020.1
Gate CI on exploit likelihood, not just severity
The headline is a new flag:
vg scan --fail-on-epss <threshold>. When any advisory's EPSS score (the probability it's exploited in the wild) meets or beats your threshold, the scan exits 2, so you can fail a build on the vulnerabilities that actually matter rather than every scary-looking CVSS number. Scan docs: https://vibgrate.com/cli/docs/scan-commandvg scan --fail-on-epss 0.1 # fail when any advisory has >=10% exploit probabilitySmaller things you'll notice
vg sbom exportnow marks development and optional dependencies correctly. Docs: https://vibgrate.com/cli/docs/sbom-commanddriftBudgetvalues, vg now warns and tells you which file said what.vg report --format htmlshows unmeasured DriftScores asn/ainstead of a misleading number.vg fixleaves an advisory open and restores your manifest and lockfile if an upgrade fails for any reason.vg serve --reviewrejects invalid document IDs and paths.vg buildnow reads each project directory once for lockfile checks and source discovery.Try it
npm install -g @vibgrate/cli vg --version # expect 2026.1020.1 vg scanNo-install try:
npx @vibgrate/cli scanBenchmarks (honest)
Two-arm benchmark vs
2026.1014.1on the pinned corpus (236 metrics compared). Extraction held steady (19 languages, 27,156 definitions, 19,978 call edges, locate accuracy 0.94, dependency detection 0.96), and startup median stayed at ~789 ms. Four small regressions, published rather than hidden: token reduction vs baseline agent 0.26 → 0.26 (−1.1%), tasks passed on both arms 37 → 36, comparable-task rate 0.97 → 0.95, and median tool calls per task with vg 6 → 7. Details: https://vibgrate.com/cli/benchmarksDiscuss
--fail-on-epss? Tell us what threshold you settled on and why. We'd love real-world numbers.— maintainers (
vibgrate-team)All reactions