Update security analysis guidelines with examples#641
Merged
masc2023 merged 1 commit intoeclipse-score:mainfrom Apr 9, 2026
Merged
Update security analysis guidelines with examples#641masc2023 merged 1 commit intoeclipse-score:mainfrom
masc2023 merged 1 commit intoeclipse-score:mainfrom
Conversation
Clarify the purpose of security analysis for features and components. Signed-off-by: Chidananda Swamy R <chidananda.swamy@ltts.com>
|
The created documentation from the pull request is available at: docu-html |
Chidananda-Swamy
requested review from
PandaeDo,
aschemmel-tech,
masc2023 and
pahmann
as code owners
masc2023
approved these changes
Apr 9, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Clarify the purpose of security analysis for features and components.
issue: #409