Skip to content

Feature/402 nox session report resolved security issues#770

Open
ckunki wants to merge 25 commits intomainfrom
feature/402-Nox_session_report_resolved_security_issues
Open

Feature/402 nox session report resolved security issues#770
ckunki wants to merge 25 commits intomainfrom
feature/402-Nox_session_report_resolved_security_issues

Conversation

@ckunki
Copy link
Copy Markdown
Contributor

@ckunki ckunki commented Apr 13, 2026

Closes #402
Closes #771

Checklist

Note: If any of the items in the checklist are not relevant to your PR, just check the box.

For any Pull Request

Is the following correct:

  • the title of the Pull Request?
  • the title of the corresponding issue?
  • there are no other open Pull Requests for the same update/change?
  • that the issue which this Pull Request fixes ("Fixes...") is mentioned?

When Changes Were Made

Did you:

  • update the changelog?
  • update the cookiecutter-template?
  • update the implementation?
  • check coverage and add tests: unit tests and, if relevant, integration tests?
  • update the User Guide & other documentation?
  • resolve any failing CI criteria (incl. Sonar quality gate)?

When Preparing a Release

Have you:

  • thought about version number (major, minor, patch)?
  • checked Exasol packages for updates and resolved open vulnerabilities, if easily possible?

)
audit(nox_session)
# Proposal: Remove this test and the related nox task under test
def test_audit(monkeypatch, nox_session, sample_vulnerability, capsys):
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could think about removing this test and the related Nox session under test as it is unused.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what you mean here. Could you expand on "it is unused"?

I and a few others use dependency:audit while updating dependencies step-wise. It's helpful to see which ones are still active without checking GitHub's dependabots.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, then please ignore my comment. 🙂

@ckunki ckunki temporarily deployed to manual-approval April 13, 2026 13:09 — with GitHub Actions Inactive
@ckunki ckunki deployed to manual-approval April 14, 2026 07:22 — with GitHub Actions Active
"""

other = sample_vulnerability
vuln_entry = {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds like a good idea. Sorry, I'm a bit confused about the code changes here though.

In looking at the sample_vulneratbility, we have:

Image

So I think that to make the docstring description & intent of this fixture match the code that the values for id and aliases[0] should be flipped. Is that right?

current_vulnerabilities=[flipped_id_vulnerability]
)
assert resolved._is_resolved(sample_vulnerability.vulnerability) is False
assert not matcher.is_resolved(sample_vulnerability.vulnerability)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
assert not matcher.is_resolved(sample_vulnerability.vulnerability)
assert not matcher.is_resolved(flipped_id_vulnerability)

# Dict of current vulnerabilities:
# * keys: package names
# * values: set of each vulnerability's references
self._references = {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that this might be problematic as a dictionary based on the package.name. For a given package & version, we might have multiple unique vulnerability issues. This vulnerabilities might be resolved in different ways and not relate to one another at all.

1 (package-version combination): m (vulnerabilities)
m (vulnerabilities) : n (resolved package-version combinations)

)
audit(nox_session)
# Proposal: Remove this test and the related nox task under test
def test_audit(monkeypatch, nox_session, sample_vulnerability, capsys):
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what you mean here. Could you expand on "it is unused"?

I and a few others use dependency:audit while updating dependencies step-wise. It's helpful to see which ones are still active without checking GitHub's dependabots.

Co-authored-by: Ariel Schulz <43442541+ArBridgeman@users.noreply.github.com>
Co-authored-by: Ariel Schulz <43442541+ArBridgeman@users.noreply.github.com>
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Need to add input to report.yml Create nox task to detect resolved GitHub security issues

2 participants