lynndylanhurley / lynndylanhurley/devise_token_auth
Security issue disclosure
Open
Nobody has claimed this yet.
close-in-7-days
- Dominant language
- Ruby
- Stars
- 3.6k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
hey I found a security issue in this repo and I don’t want to share the details here in public if you’ve got a security policy I can follow let me know otherwise I can send it over by email or whatever way works best for you
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
No files, tests, or implementation entry points are identified in the issue. Start by checking the repository's existing security guidance and reporting channels; the work is complete only when maintainers provide a documented private disclosure process or an appropriate contact path.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100