-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify And Fix NPM Vulnerabilities In All Repositories - mid-September #2532
Identify And Fix NPM Vulnerabilities In All Repositories - mid-September #2532
Comments
@HalcyonJAC @tomlovesgithub I've created a duplicate of this ticket for September - perhaps we could make that the responsibility of whoever is working on the current ticket to make a duplicate for the next month? |
New tickets will be created for any vulnerability that are found by running audit checks against each repo, and will be estimated individually. |
Fixes were applied to the following repos: apply: jac-uk/apply#1222 |
@drieJAC Is this task complete for September? If so, can a duplicate be created for October and this ticket closed pls? |
Background
Identify and fix NPM vulnerabilities in all repos. This should be conducted in the middle of the month to ensure it is regular. Once completed, the ticket should be duplicated and renamed for the next sprint.
User Story
For all repositories, on a monthly basis and as a developer, I want to run NPM audit checks to expose any new NPM vulnerabilities and fix them to prevent ongoing security issues from package dependencies.
Feature(s) Description
Ensure there are no vulnerabilities in the following repos:
The text was updated successfully, but these errors were encountered: