chore: add ossf workflow and security policy #35
Merged
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
jharlow-intel
force-pushed
the
chore/openssf-scoring
branch
from
284cd89 to
bd900e5
Compare
ZzEeKkAa
approved these changes
Aug 15, 2024
Don't think so. We're only concerned about the default branch for this Security Policy file I believe |
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.
This adds a basic, suggested template for Intel security reporting and OpenSSF check workflow.
It is the only thing missing for this repo in order for us to hit our OpenSSF scoring goals
Please read the following links:
https://securityscorecards.dev/viewer/?uri=github.com/IntelPython/dpcpp-llvm-spirv
https://wiki.ith.intel.com/display/SecTools/OpenSSF+Scorecard+Checks#OpenSSFScorecardChecks-ChecksWithMinimumScoreof0
https://github-vul-scan.intel.com/orgs/IntelPython/repos/dpcpp-llvm-spirv/openssf