bundler-alive checks if gems in a RubyGem's Gemfile.lock are active.
Currently, GitHub.com and GitLab.com are supported as a source code repository. If the source code repository is archived, then reports as not alive.
$ gem install bundler-alive
$ bundle-alive
6 gems are in Gemfile.lock
..W....
Get all source code repository URLs of gems are done!
.....
Errors:
[bundle-alive] Not found in RubyGems.org.
Archived gems:
Name: journey
URL: http://github.com/rails/journey
Total: 6 (Archived: 1, Alive: 4, Unknown: 1)
Not alive gems are found!
Default Gemfile.lock location is in your current directory. You can specify it.
$ bundle-alive -G /path/to/Gemfile.lock
You MUST set environment variables to access source code repository services.
| Repository service | ENV variable |
|---|---|
| GitHub | BUNDLER_ALIVE_GITHUB_TOKEN |
| GitLab | BUNDLER_ALIVE_GITLAB_TOKEN |
You can ignore certain gems.
$ bundle-alive -i journey rubocop-junit-formatter
The URL for some gems in RubyGems.org may have changed. You can follow the URL (default: doesn't follow).
$ bundle-alive --follow_redirect
In some cases, some gems cannot find the URL of their source code repositories. For this case, you can specify a mapping between the gem and its URL.
Put .bundler-alive.yml in your current directory. The following code is the sample.
---
gems:
coffee-script-source:
url: https://github.com/jashkenas/coffeescript/You can also specify the file path.
$ bundle-alive -c /path/to/.bundler-alive.yml
.bundler-alive.default.yml may also be helpful. Considering that having these mappings obtained automatically in the future.
Bug reports and pull requests are welcome on GitHub at https://github.com/kyoshidajp/bunlder-alive.
This gem was inspired by the following products.