feat: add check for noSensitiveInfoInRepositories
#191
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
…eInfoInRepositories'
…entage of repositories without secret scanning
…wn secret scanning statuses
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
UlisesGascon
changed the title
noSensitiveInfoInRepositoriesnoSensitiveInfoInRepositories
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.
Main Changes
This PR includes all the awesome work done by @bjohansebas in #184 ✨
I added some small changes (0c75a60, 649e7e6, e5c3959 and bc8d611) and two refactors (f4d4474 and 8798ce4) for the way the data is processed and collected (ref1) 📦
Context
noSensitiveInfoInRepositories#184noSensitiveInfoInRepositories#67noSensitiveInfoInRepositoriesopenpathfinder.com#33