lynndylanhurley / lynndylanhurley/devise_token_auth
Add gem/dependencies vulnerabilities control
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3.6k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
As [gemnasium is deprecated](https://github.com/lynndylanhurley/devise_token_auth/pull/1190), we should replace it, some options:
- Enable the already included in [Github through configuration](https://help.github.com/articles/choosing-the-delivery-method-for-your-notifications/#choosing-the-delivery-method-for-security-alerts-for-vulnerable-dependencies), if you @lynndylanhurley can, that would be great, you can disable email notifications so you aren't flooded with emails.
- [Snyk](https://github.com/marketplace/snyk)
- Gitlab CI gemnasium replacement
I will go with the first one due to its simplicity
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with GitHub's vulnerable dependency alerts configuration linked in the issue and confirm whether it can replace the deprecated Gemnasium setup. Done means dependency vulnerability monitoring is enabled without unwanted email notifications; the issue does not name a repository file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, ruby
- Domain
- security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100