Contact
Jostraca is maintained in the open. Every route below is public, and the issue tracker is the one to reach for first.
Bugs and questions
Open an issue on the generator's issue tracker. That is the primary support channel, and where an answer is most likely, because the answer stays where the next person will find it.
A good report names the version you are on, whether you are using the TypeScript package or the Go module, and the smallest generator that shows the problem. Both implementations are held to a shared test corpus, so if something differs between them, report it separately. A divergence is a bug even when neither side is obviously wrong.
Corrections to this documentation
The pages on this site are generated from the generator repository, not written here, so a correction belongs upstream where the examples are executed against the code. Open an issue or a pull request on the generator and the fix reaches this site on the next sync.
Something wrong with the site itself - a broken link, a rendering problem, an accessibility fault - belongs on the site repository instead.
Security
Report a suspected vulnerability privately through GitHub's private advisory form rather than a public issue, so a fix can be prepared before the details are public. Please include the version affected and, where you can, a minimal reproduction. You will get an acknowledgement; this is a small open source project rather than a company with a staffed security desk, so please size your expectations accordingly.
The maintainer
Jostraca is written and maintained by Richard Rodger. For anything that genuinely does not fit a public issue - a commercial question, a conversation you cannot have in the open - the contact routes on his site are the way through.
There is no phone line and no postal desk: this is an open source project, and the issue tracker is the answer to "how do I reach you". The machine-readable version of this page is /contact.md, and the site's contact point is published in the JSON-LD on the home page.