Integrating Snyk Analysis Tool (attempt 2) #91
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request for integrating snyk, a static security analysis tool, with the codebase. Snyk scans the dependencies of the codebase for vulnerabilities (security risks) and provides code security analysis on the app.snyk.io website.
This is a second attempt, the first being pull request #88 which failed deployment, could have been due to the earlier commits having edited gitignore and commented out package.json.
1. Process:
npm install -g snyk
, then made a snyk account withsnyk auth
to be able to run tests, then finallysnyk test
to run the test scan, where the output is given in the terminal (screenshots below).2. Changed files:
install/package.json: manually added the tool in dev dependencies with
"snyk": "^1.1294.0"
to address NPM install error..install/snyk: created a new file to add the dependencies snyk should ignore (with specifying the reason for ignoring) (has to be in the same directory as package.json, so added it under install).
.github/workflows/snyk.yaml: file to integrate Snyk in the github actions workflow, specifying the severity threshold of vulnerability risks to test (high vulnerability) and the frequency of running tests (every PR).
3. Terminal output screenshots (after resolving vulnerabilities by updating):