-
Notifications
You must be signed in to change notification settings - Fork 9
Decouples security scanning analysis and add FOSSA #110
Conversation
leordev
commented
Dec 5, 2023
- We are decoupling the security scanning to be able to run security checks on approved forks
- Plus, taking the opportunity to add FOSSA because we are assessing their security tooling and SBOMs generation
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
|
.github/workflows/security.yml
Outdated
push: | ||
branches: | ||
- main | ||
- leordev/* # todo: remove this line before merging |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we're doing both Snyk and FOSSA? There is overlap there, yeah? But I presume they both offer their own distinct value-adds
Yes! They overlap but we are experimenting both to decide which one to adopt, or either move on with both for having double security layers. FOSSA provides SBOMs and Rust, Snyk provides advanced static analysis... So we are playing with both things! |