-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Violations support for JAS scanners #241
Merged
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
…dded the new parsed violations results to ApplicabilityScanManager.
…ew parsed violations results to IacScanManager.
…new parsed violations results to SastScanManager.
…e new parsed violations results to SecretScanManager.
…ded relevant logs
…methods for hte new struct
eranturgeman
had a problem deploying
to
frogbot
November 19, 2024 10:47 — with
GitHub Actions
Failure
…o jas-violations-support
eranturgeman
had a problem deploying
to
frogbot
November 19, 2024 10:48 — with
GitHub Actions
Failure
…canner cannot incur violations
…y commented at this point)
…o delete comments in results.go)
…rseCommandResults related to jas violations
…esults) + changed the names for Sca parsing methods
…all relevant references
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 26, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 26, 2024
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 29, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 29, 2024
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 29, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 29, 2024
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 29, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 29, 2024
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 31, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 31, 2024
hadarshjfrog
approved these changes
Dec 31, 2024
7 tasks
attiasas
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 31, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 31, 2024
Merging this branch will not change overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
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.
dev
branch.go vet ./...
.go fmt ./...
.Depends on:
Add Support for JAS violations
1. Allow generating JAS violations in the scan by providing
watch
,GitRepositoryKey
, orproject
attributes.GitRepositoryKey
: the http/https git clone url of the repository the code related to. (The actual expected value is converted by removing the protocol)Xray
(SCA scan) and to theanalyzerManager
(JAS scans)2. Generating violations in all output formats (adding attributes to tables/structs where needed)
3. Violations should also be generated for binary scans that support JAS (passing the
project key
to theanalyzerManager
)4. In Frogbot,
GitRepositoryKey
is always passed to the command, this means the user will start to see only violations and not vulnerabilities as the default behavior without supplying any arguments, to avoid breaking:GitRepositoryKey
we will fetch the active watches on this resource, if non exists we will show vulnerabilities (only if the user did not request any other params likewatches
\project key
\repo path
...)Additional changes
resultsContext
struct to replacecommonGraphScanParams
to hold and handle all the attributes that can be used to generate results (watches, project key, git repo ....)ScanResult[T interface{}].StatusCode
(not performed = nil
,completed = 0
,failed != 0
)convertor_test.go
jf scan
/jf docker scan
) when--repo-path
is presentJFROG_SECURITY_CLI_TESTS_JFROG_PLATFORM_PROJECT_KEY
AnalyzerManager
version to1.13.2