Skip to main content
Back to Tags

Vulnerabilities

12 items tagged with "vulnerabilities"

Filter by type:

FAQs8

FAQ

How do I gate pull requests on known vulnerabilities with GitHub Actions?

Use the maintained vibgrate/cli Action: `uses: vibgrate/cli@v1` with `vulns: true`, `fail-on: error`, and `upload-sarif: true`. It scans installed dep...

FAQ

What is a CVE and what is CVSS?

A CVE (Common Vulnerabilities and Exposures) is a unique public identifier, such as CVE-2021-44228, assigned to a specific known security vulnerabilit...

FAQ

How do I scan for known vulnerabilities?

Run `vg scan --vulns`. It matches every installed dependency against the public OSV database and reports known vulnerabilities with advisory id and CV...

FAQ

Can I scan for vulnerabilities offline or air-gapped?

Yes. `vg scan --vulns` queries the OSV database over the network by default, but you can supply advisories in a package-version manifest and run fully...

FAQ

Which ecosystems support vulnerability detection and attribution?

Detection and attribution read each project's lockfile, covering npm / pnpm / yarn, pip / poetry / pipenv, cargo, composer, bundler, go, pub, hex, NuG...

FAQ

What are CRA remediation metrics?

When `vg scan --vulns` runs in a git repository, Vibgrate attributes each vulnerability to the commit that introduced the affected version and measure...

FAQ

Does Vibgrate measure real mean time to remediate (MTTR)?

Yes. As well as how long open vulnerabilities have been exposed, Vibgrate reconstructs closed exposure windows from git history — a vulnerable version...

FAQ

What does vg scan --full do?

`vg scan --full` runs a comprehensive scan in one command: the normal DriftScore, known-vulnerability detection (the same as `--vulns`), and, when a s...