Skip to content
This repository has been archived by the owner on Feb 25, 2023. It is now read-only.

Static Analysis of code #30

Open
bagmangood opened this issue Jun 26, 2017 · 5 comments
Open

Static Analysis of code #30

bagmangood opened this issue Jun 26, 2017 · 5 comments

Comments

@bagmangood
Copy link
Contributor

Gemsurance currently requires both the ruby version and all of the dependencies installed in order to run the check.

Ideally you could run the check with only needing to install gemsurance

@martinstreicher
Copy link

I don't understand this. The Gemfile specifies the Ruby version, too.

@bagmangood
Copy link
Contributor Author

I was attempting to use gemsurance to generate safety reports in CI. Gemsurance's current mechanisms require all of your project's dependencies to be currently installed.

Ideally you'd be able to only have ruby and gemsurance installed in an environment and still be able to generate the gemsurance report.

@martinstreicher
Copy link

martinstreicher commented Dec 6, 2018 via email

@bagmangood
Copy link
Contributor Author

yup - that was what I was aiming for. I think it might require a substantial re-write of the internals, since right now gemsurance leverages bundler's code for wrapping all of the calls to rubygems.

@jonkessler
Copy link
Contributor

I think that could make sense as an additional use case, but I wouldn’t replace the way it’s currently done.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants