grape vulnerabilities
A Ruby framework for rapid API development with great conventions.
- Registry
- RubyGems
- Latest
- 4.1.0
- License
- MIT
1 known advisory
The latest version, 4.1.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
bundle update --conservative grape # Gemfile: '>= 4.1.0'Is your project on an affected grape?
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 grape
grape subject to Cross-site Scripting
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Is your grape version vulnerable?
- grape 4.1No known advisories in 4.1.0
- grape 4.0No known advisories in 4.0.1
- grape 3.3No known advisories in 3.3.5
- grape 3.2No known advisories in 3.2.1
- grape 3.1No known advisories in 3.1.1
- grape 3.0No known advisories in 3.0.1
- grape 2.4No known advisories in 2.4.0
- grape 2.3No known advisories in 2.3.0
- grape 2.2No known advisories in 2.2.0
- grape 2.1No known advisories in 2.1.3
- grape 2.0No known advisories in 2.0.0
Which of your client projects still run an old grape?
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.