-
Notifications
You must be signed in to change notification settings - Fork 506
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
✨ Feature DependencyDiff (Version 0 Part 2) #2046
Conversation
Integration tests success for |
Integration tests success for |
Integration tests success for |
Integration tests success for |
Integration tests success for |
Integration tests success for |
* temp * Update dependencies.go * Update errors.go * Update scorecard_results.go * Update vulnerabilities.go * save * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp * temp0713-1 * temp0713-2 * temp0713-3 * temp0713-4 * temp0713-4 * temp0713-5 * temp0713-6 * temp0713-7 * temp0713-8 * temp0713-9 * temp0713-10 * temp0713-11 * temp0713-12 * 1 * temp * temp * temp * temp * temp * temp * temp * temp * save * save * save * final_commit_before_merge
What kind of change does this PR introduce?
This is a follow-up PR of PR #2030, introducing the main Dependency-diff API to the Scorecard repo.
Detailed changes include:
GetDependencyDiffResults
used to fetch Scorecard results for dependency changes between two code commits and return the dependency check results (with scorecard results included);FetchDependencyDiffData
used to get dependency-diffs between two code commits;Dependency
struct used for receiving raw data from the dependency-diff source (currently we are using the GitHub Dependency Review API);AsJSON
support forDependencyCheckResult
, making it JSON-dump-able;What is the current behavior?
In version 0 part 1 (PR #2030), only the exported result structure
DependencyCheckResult
was introduced.What is the new behavior (if this is a feature change)?**
Introduce subsequent functions and structures of this feature.
Which issue(s) this PR fixes
This is a part of the issue #2008.
Does this PR introduce a user-facing change?
No.
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)