Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: packetchaos/navi
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: nbycomp/navi
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: severy_modification_type_nevi
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 2 files changed
  • 1 contributor

Commits on Jan 30, 2026

  1. config update: Add severity_modification_type option 

    Allow to select the vulnerabilites to be imported to the NAVI DB based
on the recast done by the user. Default behaviour continues to export
all vulnerabilities.

The --severity-modification-type option in the `navi config update` command
allows to select the vulnerabilities based on the user recast action:

- NONE: No modification to the severity has been made.
- RECASTED: A user has recast the risk associated with the vulnerability.
- ACCEPTED: A user has accepted the risk associated with the vulnerability.

This can be used in cases where users are syncing the exports with
external ticketing systems (e.g. github, jira,...), considering only the
ones to be fixed and not accepted.

Signed-off-by: Josep Lluis Ferrer <jlferrer@nearbycomputing.com>
    @jlferrer
    jlferrer committed Jan 30, 2026
    Configuration menu
    Copy the full SHA
    fda00ba View commit details
    Browse the repository at this point in the history
Loading