Thanks for the idea, it really makes sense, so we’re starting to evaluate how to implement this.Fabio commented
You should really provide an option to behave like `bundle outdated --strict`.
Sometimes one pin a gem to a specific version because his code is not compatible with the next (either minor or major) version.
Or maybe the new version has an issue that prevent your code to work as expected.
Bundle already handle this, with `bundle outdated --strict`
Ideally gemnasium should resemble the output of the previous command. It should only warn when current dependencies have security issues, otherwise badge should be green if command output is empty.Fabio supported this idea ·