Skip to content

Clean up open security PRs and resolve CVEs #109

Description

@inFocus7

We should clean up the number of PRs -- namely the security-related nones -- by closing the automated Snyk pulls. Below I have compiled a list of the PRs that can be left opened (and merged), should be closed (duplicates), and those that require more investigation.

After these merge, we should do a final CVE check to see if any lingering, resolvable CVEs exist.


Can be kept... (5 + 1)

Can be closed... (19)

Ideal // Investigation Needed (2)

Here due to breaking changes requiring more investigation...
These would be the ideal versions, as opposed to above, but there were notes in the PRs regarding breaking changes requiring more investigation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions