Contact Us

Questions, feedback, bug reports, partnership inquiries — here’s how to reach us.

Email

brian@krypton-lang.org

For general questions, partnership / collaboration inquiries, or anything that isn’t a bug report.

Other ways to reach us

Bug reports

Found a bug, a crash, or unexpected behavior in the compiler or standard library? Open an issue on GitHub. Include a minimal reproducer if you can — the smaller the test case, the faster we can fix it.

github.com/t3m3d/krypton/issues →

Feature requests

Have an idea for a new builtin, language feature, or backend? Open a discussion or issue on GitHub. Even half-formed proposals are welcome — the language is small enough that good suggestions often land quickly.

Open an issue →

Contributions

Pull requests are welcome. Browse the repo, read CHANGELOG.md for context on recent work, and fork from main. New builtins, examples, algorithms, and stdlib modules are all good places to start.

View the repo →

Documentation

Most “how does X work” questions are already answered in the language spec, the function reference, or one of the 25 tutorial lessons. Worth a quick look before you reach out.

Read the spec →

Krypton is developed by a small team. Email and GitHub issues are monitored regularly — expect a response within a few days.