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

[August 2023] eRegs parsing requirements #777

Closed
4 tasks done
Tracked by #137
pkfec opened this issue Jul 27, 2023 · 0 comments · Fixed by #783
Closed
4 tasks done
Tracked by #137

[August 2023] eRegs parsing requirements #777

pkfec opened this issue Jul 27, 2023 · 0 comments · Fixed by #783
Assignees
@tmpayton
Labels
Security: general General security concern or issue
Milestone
Sprint 22.4

Comments

@pkfec
Copy link
Contributor

pkfec commented Jul 27, 2023 •
edited by tmpayton
Loading

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

Reference ticket: #772

Action Items :

  • Check and document parsing requirements and upgrades in Snyk
    • Run: snyk test --file=requirements-parsing.txt --package-manager=pip

Completion criteria:

  • Upgrade vulnerable packages in requirements-parsing.txt
  • Setup and parse 2022 regulations on local environment
  • Create a new ticket to check for the month of September 2023
@pkfec pkfec added the Security: general General security concern or issue label Jul 27, 2023
@pkfec pkfec added this to the Sprint 22.4 milestone Jul 27, 2023
@tmpayton tmpayton self-assigned this Aug 16, 2023
This was referenced Aug 22, 2023
Merged
Closed
@patphongs patphongs mentioned this issue Feb 29, 2024
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tmpayton tmpayton

Labels
Security: general General security concern or issue
Projects
None yet
Milestone
Sprint 22.4
Development

Successfully merging a pull request may close this issue.

upgrade parsing requirements fecgov/fec-eregs
2 participants
@pkfec @tmpayton