Fixed bug: generate criticality_score #58
Merged
Conversation
This file contains hidden or 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
added 2 commits
February 8, 2024 11:56
pramit-d
pushed a commit
that referenced
this pull request
Feb 9, 2024
* Update generate metadata (#56) * Fixed metadata generate issue for Be-Secure origin projects * Updated dev-kit according to the new besecure-asset-store path * Fixed bug: generate criticality_score (#58) * Fixed code for criticality score * removed discontinued version of criticality_score * Update README.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixed #57
Root cause: Due to some internal issues of the criticality_score package users were getting errors in BeS-dev-kit.
Resolution: Previously BeS-dev-kit was installing criticality_score through pip. The mentioned criticality_score package has been discontinued. So ossf will not provide support for the version we are using. Currently, ossf suggesting to install the package using Go. So changed the installation procedure in BeS-dev-kit.