Batuhan Apaydın
Batuhan Apaydın
>integrating it in ko probably looks like running govulncheck on the importpath being built (govulncheck ./cmd/controller) while building It means that ko will require `golvuncheck` to be installed in the...
> To directly integrate vulnerability checking into other tools and processes, the [vulncheck](https://pkg.go.dev/golang.org/x/vuln/vulncheck) package exports govulncheck’s functionality as a Go API. ^ https://go.dev/blog/vuln#vulnerability-detection-using-govulncheck
we can work in a collaboration @ChaosInTheCRD, WDYT?
> I believe you also need the `-t` flag, but in general I believe interactive commands don't quite work when going through `terratest` because of the way the logging infrastructure...
cc: @dentrax @eminaktas @necatican @yasintahaerol @f9n
please feel free to assign it to me. I'm willing to work on it.
https://github.com/developer-guy/kubescape/runs/4888848092?check_suite_focus=true You can follow up the process here @slashben, seems working, I'll prepare a PR ASAP, but, you can verify the kubescape binary I've built via the following command: ```shell...
you can assign it to me @dwertent, I'll take care of that
Unfortunately, the problem still exists, to reproduce the same issue here[^1]: 1. replace the base image definition defined in .ko.yaml with: `cgr.dev/chainguard/static:latest` 2. build the container image by simply running:...
> Does bom expect the go executable to be present? yep, this is why we set the current base image of the bom project as _ghcr.io/chainguard-images/go:latest_ [here](https://github.com/kubernetes-sigs/bom/blob/main/.ko.yaml#L1).