Skip to content
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

Static Code Analysis #187

Closed
hoeltcl opened this issue Aug 14, 2019 · 2 comments
Closed

Static Code Analysis #187

hoeltcl opened this issue Aug 14, 2019 · 2 comments
Labels

Comments

@hoeltcl
Copy link

hoeltcl commented Aug 14, 2019

Gardener informs its stakeholders in its CNCF CII Badge, that static code checks are applied by using Checkmarx. This repository has findings, which have to be assessed by the component owner(s). As required all prio high findings were already been immediately assessed. Please find the timeline until when to assess the remaining prio medium findings in the Wiki (restricted access). At the time being you can ignore the prio low findings. Please find background information and a link to the Checkmarx project for your repository in the Wiki (restricted access). In the Wiki (restricted access) you will as well find information how to get a Checkmarx user which is required to be able to do your assessment in the Checkmarx Web UI.

@hoeltcl hoeltcl added the kind/bug Bug label Aug 14, 2019
@shreyas-s-rao
Copy link
Collaborator

The latest scan result from Checkmarx recommends addressing a task that is part of a larger issue #189 which is now being worked upon.

@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 21, 2019
@swapnilgm
Copy link
Contributor

Fixed via #196

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants