Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

[March] eRegs parsing requirements #672

Closed
4 tasks done
pkfec opened this issue Mar 1, 2022 · 0 comments · Fixed by #683
Closed
4 tasks done

[March] eRegs parsing requirements #672

pkfec opened this issue Mar 1, 2022 · 0 comments · Fixed by #683
Assignees
@cnlucas
Milestone
PI 17 innovation

Comments

@pkfec
Copy link
Contributor

pkfec commented Mar 1, 2022 •
edited by cnlucas
Loading

Take a look at Snyk vulnerabilities for requirements-parsing.txt and upgrade relevant packages to maintain the parsing tool

requirements-parsing.txt: 1 High

Completion criteria:

  • Check and document parsing requirements and upgrades in Snyk
  • Upgrade packages where necessary
  • Create a ticket to check for the month of April
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cnlucas cnlucas

Labels
None yet
Projects
None yet
Milestone
PI 17 innovation
3 participants
@johnnyporkchops @pkfec @cnlucas