You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we are reluctant to integrate new scanners because that automatically means that we have to maintain them. However, this issue comes from one of our core contributors, I will discuss this in the team.
Until then, you could try integrating this scanner yourself. The secureCodeBox can integrate any scanner container. This means that the code does not necessarily have to be in our repo.
There is already the idea of establishing community scanners: #915
we discussed this issue in the team: Integration of Gobuster has very low priority for us at the moment because we think that this particular scanner is hard to automate. In our opinion Gobuster is a great tool for manual and custom penetration testing.
If you do an integration on your own, we'll add your repo to our documentation as a community scanner.
If you need some help, feel free to start a discussion here or join our channel "project-securecodebox" in the OWASP Slack.
Activity
[-]## 🚓 Integrate busting tool gobuster[/-][+]🚓 Integrate busting tool gobuster[/+][-]🚓 Integrate busting tool gobuster[/-][+]🚓 Integrate directory busting tool gobuster[/+]Upgrading kubeaudit from v0.14.2 to v0.15.0
Freedisch commentedon Nov 14, 2023
@Weltraumschaf, I would like to help on this if this issue is still active
Weltraumschaf commentedon Nov 17, 2023
Hi @Freedisch, thanks for your offer.
At the moment we are reluctant to integrate new scanners because that automatically means that we have to maintain them. However, this issue comes from one of our core contributors, I will discuss this in the team.
Until then, you could try integrating this scanner yourself. The secureCodeBox can integrate any scanner container. This means that the code does not necessarily have to be in our repo.
There is already the idea of establishing community scanners: #915
Freedisch commentedon Nov 17, 2023
Alright, thanks for the reply. I will look into it
Weltraumschaf commentedon Nov 28, 2023
Hi @Freedisch,
we discussed this issue in the team: Integration of Gobuster has very low priority for us at the moment because we think that this particular scanner is hard to automate. In our opinion Gobuster is a great tool for manual and custom penetration testing.
If you do an integration on your own, we'll add your repo to our documentation as a community scanner.
If you need some help, feel free to start a discussion here or join our channel "project-securecodebox" in the OWASP Slack.
Weltraumschaf commentedon Feb 9, 2024
We close this issue because we have no plans to add this scanner in the near future.