-
Notifications
You must be signed in to change notification settings - Fork 113
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
feat: request cve automatically #777
Merged
RafaelGSS
merged 12 commits into
nodejs:main
from
marco-ippolito:feat/automate-cve-creation
Apr 4, 2024
Merged
feat: request cve automatically #777
RafaelGSS
merged 12 commits into
nodejs:main
from
marco-ippolito:feat/automate-cve-creation
Apr 4, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marco-ippolito
force-pushed
the
feat/automate-cve-creation
branch
2 times, most recently
from
March 8, 2024 09:55
0e74e96
to
2cf417b
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #777 +/- ##
=======================================
Coverage 82.97% 82.97%
=======================================
Files 37 37
Lines 4200 4200
=======================================
Hits 3485 3485
Misses 715 715 ☔ View full report in Codecov by Sentry. |
marco-ippolito
force-pushed
the
feat/automate-cve-creation
branch
2 times, most recently
from
March 8, 2024 13:57
4f7ae71
to
4dd90a2
Compare
cc @RafaelGSS |
RafaelGSS
reviewed
Mar 19, 2024
marco-ippolito
force-pushed
the
feat/automate-cve-creation
branch
2 times, most recently
from
March 20, 2024 14:43
ae94214
to
10b3680
Compare
RafaelGSS
reviewed
Mar 21, 2024
this needs to land before: #780 |
marco-ippolito
force-pushed
the
feat/automate-cve-creation
branch
3 times, most recently
from
March 26, 2024 08:01
47a5e7e
to
6c9e091
Compare
RafaelGSS
reviewed
Mar 27, 2024
marco-ippolito
force-pushed
the
feat/automate-cve-creation
branch
2 times, most recently
from
April 1, 2024 13:53
aee7183
to
70b871c
Compare
reminder to remove |
@marco-ippolito would you mind creating a list of tasks remaining for this PR?
|
marco-ippolito
force-pushed
the
feat/automate-cve-creation
branch
from
April 4, 2024 08:32
70b871c
to
2c7a4cf
Compare
marco-ippolito
force-pushed
the
feat/automate-cve-creation
branch
from
April 4, 2024 08:38
2c7a4cf
to
be3e9e8
Compare
RafaelGSS
approved these changes
Apr 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
the command
git-node security --request-cve
will read the vulnerabilities.json and request a cve for each report, if does not find the severity in the report will try to fetch it from hackerone, we can probably make the json path optional and try to read it from the standard location