Last updated 18 August 2026
Contact
Where to send a bug report, a feed correction, a security report or anything else.
Emendant is operated by Soham Jain, an individual established in the United Kingdom. The source repository is private, so email is the route rather than an issue tracker.
| Anything about the tool | contact@emendant.com |
|---|---|
| A security problem | security@emendant.com, and the security page says what to include |
| Privacy and your data | privacy@emendant.com |
| The licence or the terms | legal@emendant.com |
A bug in the tool
Include the output of emendant --version, your operating system and Node.js version, the command you ran, and what it printed. If a scan reported something you believe is wrong, emendant explain <change-id> prints the feed entry behind it, and that output says a great deal in a small space.
A wrong or missing feed entry
A finding you believe is false, or a breaking change we do not cover, is the most useful thing you can send. Name the package, the version, and the change. A correction is published as a later snapshot, which every installed copy picks up on its next refresh without upgrading.
A security problem
Use the security page, which says what to include and what to expect.
Anything else
Questions about using Emendant inside a larger organisation, or about the feed service, are welcome at contact@emendant.com.