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

Introduce gosec for Static Application Security Testing (SAST) #948

Closed
5 tasks done
rishabh-11 opened this issue Oct 21, 2024 · 1 comment · Fixed by #954
Closed
5 tasks done

Introduce gosec for Static Application Security Testing (SAST) #948

rishabh-11 opened this issue Oct 21, 2024 · 1 comment · Fixed by #954
Assignees
Labels
area/compliance Compliance related area/security Security related kind/enhancement Enhancement, improvement, extension priority/1 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)

Comments

@rishabh-11
Copy link
Contributor

rishabh-11 commented Oct 21, 2024

How to categorize this issue?

/area compliance
/area security
/kind enhancement
/priority 1

What would you like to be added:
use gosec for SAST. Check gardener/gardener#9959 for reference.

Why is this needed:
Please look at the mail from Claudia with the title Enable security linting in your repository by end of 2024 for details.

@rishabh-11 rishabh-11 added the kind/enhancement Enhancement, improvement, extension label Oct 21, 2024
@gardener-robot gardener-robot added area/compliance Compliance related area/security Security related priority/3 Priority (lower number equals higher priority) labels Oct 21, 2024
@rishabh-11 rishabh-11 added the priority/1 Priority (lower number equals higher priority) label Oct 21, 2024
@gardener-robot gardener-robot removed the priority/3 Priority (lower number equals higher priority) label Oct 21, 2024
@thiyyakat thiyyakat self-assigned this Oct 24, 2024
@rishabh-11 rishabh-11 reopened this Nov 15, 2024
@gardener-robot gardener-robot added status/closed Issue is closed (either delivered or triaged) status/accepted Issue was accepted as something we need to work on and removed status/closed Issue is closed (either delivered or triaged) labels Nov 15, 2024
@aaronfern
Copy link
Contributor

Closing as all PRs are merged
/close

@gardener-robot gardener-robot added status/closed Issue is closed (either delivered or triaged) and removed status/accepted Issue was accepted as something we need to work on labels Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/compliance Compliance related area/security Security related kind/enhancement Enhancement, improvement, extension priority/1 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants