Pick the channel that fits
Contact
Bugs go to the issue tracker so they stay visible and become fixes. Questions can go to discussions or straight to the maintainer. There is no email link on this page because issues and discussions are the working channels for an open source tool.
preset, command used, input shape, --dry-run output, expected verdict, actual verdict (structured)
Channels
| Need | Channel |
|---|---|
| Bug or crash | GitHub issues |
| Questions and ideas | GitHub discussions |
| Direct message | X / Twitter |
| Long form |
A good issue includes the preset, the exact command, the input shape, and the dry run output. That gives the repository enough to reproduce without burning anyone's credits.
One note on responding: the maintainer works in public and the issue tracker is the archive. A question asked there remains searchable for the next person with the same setup, which is why discussions and issues outrank a private inbox for this project. For time-critical or commercial questions, the direct channels in the table are the better fit. Either way, include the command you ran; reproductions beat descriptions.
Maintainer
Akash Priyadarshi, software engineer in Patna, Bihar, India. Maintains the Jev tooling family: jev-seo, jev-git, jev-superpowers and this sifter. The ecosystem footer lists every project in the family.