Address npm audit (and dependabot?) results

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: Tech debt
    • None
    • Not Needed 

      110 vulnerabilities (30 low, 26 moderate, 45 high, 9 critical)

      Can we look at them and somehow explicitly ignore the ones we won't be fixing? Or file issues for the ones we will fix? Alternatively we can have a tool create PRs to bump these things for us, scan through the changelogs and merge PRs that are green according to CI.

            Assignee:
            Unassigned
            Reporter:
            Le Roux Bodenstein
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: