-
Updated
Oct 23, 2020 - Python
vulnerability
Here are 579 public repositories matching this topic...
-
Updated
Oct 23, 2020 - Python
-
Updated
Oct 22, 2020 - Vue
-
Updated
Oct 21, 2020 - Shell
-
Updated
Aug 28, 2020 - Java
-
Updated
Sep 10, 2020 - JavaScript
-
Updated
Oct 10, 2020 - Python
-
Updated
May 22, 2020 - Lua
-
Updated
Sep 12, 2020 - PHP
-
Updated
Sep 12, 2020 - Go
-
Updated
Oct 6, 2020 - Python
-
Updated
Oct 20, 2020 - JavaScript
-
Updated
Jul 1, 2020 - Java
-
Updated
Oct 13, 2020
-
Updated
Jul 20, 2020 - Python
-
Updated
Jun 21, 2020 - Python
-
Updated
Nov 2, 2018 - Python
-
Updated
Jun 12, 2020 - Python
-
Updated
Jan 11, 2018 - Ruby
-
Updated
Oct 23, 2020 - C
-
Updated
Oct 21, 2020
-
Updated
Feb 10, 2018 - Python
-
Updated
Sep 28, 2020 - Python
-
Updated
Aug 19, 2020 - Python
-
Updated
Jan 22, 2019 - Python
Improve this page
Add a description, image, and links to the vulnerability topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vulnerability 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 `*