🌱 Add Chromium project dependencies to automated scanning #4476
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
renewitt
requested review from
justaugustus and
spencerschrock
and removed request for
a team
renewitt
force-pushed
the
add-projects-for-scanning
branch
from
e26c18f to
0495356
Compare
spencerschrock
approved these changes
Jan 6, 2025
There was a problem hiding this comment.
The additions LGTM, but please fix the DCO on your commit:
https://github.com/ossf/scorecard/pull/4476/checks?check_run_id=35097128375
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.
What kind of change does this PR introduce?
Updates the list of projects configured for scanning to include third party open source dependencies used by the Chromium project.
What is the current behavior?
Only a subset of eligible open source projects used by Chromium as third party dependencies are scanned.
Which issue(s) this PR fixes
NONE
Does this PR introduce a user-facing change?