-
Notifications
You must be signed in to change notification settings - Fork 8
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
Critical vulnerability in socket.io-parser #801
Comments
# Pull Request ## 🤨 Rationale As described in #801 we have a vulnerability that is causing `npm audit` to fail the PR build, preventing submissions. ## 👩💻 Implementation Comment out the audit step that's failing. We'll use the bug linked above to track re-enabling it. ## 🧪 Testing PR build ## ✅ Checklist <!--- Review the list and put an x in the boxes that apply or ~~strike through~~ around items that don't (along with an explanation). --> - [x] I have updated the project documentation to reflect my changes or determined no changes are needed.
@fredvisser does Snyk replace the functionality that |
Snyk doesn't support monorepos by default, so isn't picking up any of the package specific package.json files. So the current setup isn't good enough. We could switch to a their Github Action or we could add the Github Dependency Review Action which would keep the workflow entirely with Github. |
# Pull Request ## 🤨 Rationale #801 highlighted that our current use of `npm audit` is brittle. This action should elevate any issues tracked by Github to the PR. ## 👩💻 Implementation - Use the example config file from https://github.com/actions/dependency-review-action?tab=readme-ov-file - I'll remove the Snyk integration when this PR goes in ## 🧪 Testing This PR only highlights the packages that are changed (the Github Actions), but since the [Github dependency graph](https://github.com/ni/nimble/network/dependencies) sees our other NPM dependencies, I expect this will evaluate package.json issues when a PR has those changes in it. I could add known bad issues to this PR to validate, or we could just submit this and validate over time. ## ✅ Checklist <!--- Review the list and put an x in the boxes that apply or ~~strike through~~ around items that don't (along with an explanation). --> - [x] I have updated the project documentation to reflect my changes or determined no changes are needed.
Fixed in #1930 |
@fredvisser looking at the dependency review check instructions it says to check the following page: https://github.com/ni/nimble/security/dependabot where there I see non-dismissed critical vulns, but it doesn't look like dependency review check is complaining about those, see build: and log: Edit: Ohhh, it maybe is only detecting dependency changes based on the README: https://github.com/actions/dependency-review-action?tab=readme-ov-file#dependency-review-action So that's great and it might be working fine. I'll re-close the issue |
🧹 Tech Debt
npm audit
started failing due to a new critical vulnerability in socket.io-parser. This blocks the main PR workflow.The package is pulled in by
karma
and@11y/eleventy
:The text was updated successfully, but these errors were encountered: