feat: githubSecretScanningReport #5242
Open
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
v0lkc
force-pushed
the
feat/githubSecretScan
branch
from
8e68b18 to
a3ef46c
Compare
v0lkc
force-pushed
the
feat/githubSecretScan
branch
from
a3ef46c to
ce952ad
Compare
|
|
/it-go |
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.
Description
Introducing a new piper step
githubSecretScanningReport. It aims to enhance our security and compliance capabilities by providing detailed insights into any potential secret exposures for a given GitHub repository.Output Format
The output from this step has the following format:
{ "toolName": "GitHubSecretScanning", "repositoryUrl": "https://github.com/some/repository", "secretScanningUrl": "https://github.com/some/repository/security/secret-scanning", "findings": [ { "classificationName": "Audit All", "total": 1, "audited": 0 } ] }Checklist