-
Updated
Feb 25, 2021 - Go
vulnerability-detection
Here are 196 public repositories matching this topic...
-
Updated
Jan 22, 2021 - Shell
-
Updated
Feb 25, 2021 - Go
-
Updated
Jan 29, 2020 - Python
-
Updated
Jan 28, 2020 - Ruby
-
Updated
Feb 25, 2021 - Java
-
Updated
Feb 25, 2021 - C
-
Updated
May 22, 2020 - Lua
-
Updated
Feb 23, 2021 - Python
-
Updated
Feb 12, 2021 - Python
-
Updated
Feb 24, 2021 - C
-
Updated
Nov 26, 2020 - BitBake
-
Updated
Jan 4, 2021 - Python
-
Updated
Feb 23, 2021 - Python
-
Updated
Feb 3, 2021 - Perl
-
Updated
Feb 10, 2018 - Python
-
Updated
Jan 6, 2021 - Python
-
Updated
Feb 19, 2021 - Shell
The current swagger definition is autogenerated. The automatically generated definitions rely on reflection and annotations to create the documentation. The reflection capabilities are poor at best and lead to missing API parameters. Annotations can help in some cases, but the only fix for Swagger is to create individual POJOs for every possible request. This will lead to unnecessary large number
-
Updated
Feb 22, 2021
-
Updated
Jan 10, 2020 - JavaScript
-
Updated
Jan 7, 2021 - Python
-
Updated
Feb 20, 2021 - Ruby
-
Updated
Apr 20, 2020 - Python
Feedback
I think that you are doing a very necessary system and your idea is cool, but at the moment it has a lot of bugs. From what I noticed, the assets do not understand the ascii characters and the system crashes. In addition, I did not find a description of the API, I would like to integrate your system into TheHive, or rather make it possible to view information about an asset in TheHive. I believe t
-
Updated
Feb 23, 2021
-
Updated
Feb 3, 2021 - Python
-
Updated
Feb 25, 2021 - Python
-
Updated
Sep 28, 2018 - Python
Improve this page
Add a description, image, and links to the vulnerability-detection topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vulnerability-detection topic, visit your repo's landing page and select "manage topics."
Currently, Trivy traverses all paths and looks for all Gemfile.lock in a container image. However, the image sometimes has only Gemfile.lock and doesn't install gems listed in the Gemfile.lock. I think a gem should have *.gemspec file if it is installed. e.g.
rake.gemspechas the information aboutrake.To avoid false positives from Gemfile.lock, we are probably able to take advantage of `*