guard-livereload vulnerabilities
Guard::LiveReload automatically reloads your browser when 'view' files are modified.
- Registry
- RubyGems
- Latest
- 2.5.2
- License
- MIT
1 known advisory
The latest version, 2.5.2, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
bundle update --conservative guard-livereload # Gemfile: '>= 2.5.2'Is your project on an affected guard-livereload?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for guard-livereload
guard-livereload has a directory traversal vulnerability
- Affected
- <2.5.2
- Fixed in
- 2.5.2
Is your guard-livereload version vulnerable?
- guard-livereload 2.5No known advisories in 2.5.2
- guard-livereload 2.41 advisory in 2.4.0
- guard-livereload 2.31 advisory in 2.3.1
- guard-livereload 2.21 advisory in 2.2.0
- guard-livereload 2.11 advisory in 2.1.3
- guard-livereload 2.01 advisory in 2.0.1
- guard-livereload 1.41 advisory in 1.4.0
- guard-livereload 1.31 advisory in 1.3.0
- guard-livereload 1.21 advisory in 1.2.1
- guard-livereload 1.11 advisory in 1.1.3
- guard-livereload 1.01 advisory in 1.0.3
- guard-livereload 0.41 advisory in 0.4.2
- guard-livereload 0.31 advisory in 0.3.1
- guard-livereload 0.21 advisory in 0.2.1
- guard-livereload 0.11 advisory in 0.1.11
Which of your client projects still run an old guard-livereload?
NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other RubyGems packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.