Skip to content

Improve CLI and logging output when there is no report or a NIST API error occurs #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mmaass-torc
Copy link

Basically:

  1. If there are no CVEs there will be report generated. When this occurs, CVE Tracker silently terminates. This causes people who are new to CVE Tracker, or who haven't used it in a while, to wonder if the tool worked at all. This PR adds a new output message to remedy that.

  2. When the NIST search request results in an error response, CVE Tracker failed to check for CVEs in a particular module. There may be CVEs, we just don't know because the query failed. This PR updates the log message used when this error occurs to state the module name that was queried so that a reader of a partial report knows a module is missing solely because the request failed, not because the module is free of CVEs.

mmaass-torc added 2 commits April 11, 2025 12:56
…report. Adding this because otherwise it's not clear CVE Tracker did anything. It just silently terminates.
…ich modules were not successfully searched for.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant