Contact

Blunt Code is developed in the open — the fastest way to reach the project is the GitHub repository. There is no support email or hotline; everything happens in the issue tracker where reports are public and searchable, which also serves anyone hitting the same problem later.

Bugs and feature requests

Open an issue at github.com/sanketpatel32/Blunt-code/issues. A good report includes: the version shown in the app’s About panel, your Windows version, the smallest folder or command that reproduces the problem, and what you expected instead. If a scan failed or crashed, the per-launch logs under %LOCALAPPDATA%\BluntCode\logs usually contain the exact analyzer error — attaching the newest log file turns “it broke” into a fixable report. Feature requests are welcome in the same tracker; check the changelog first in case the behavior already changed in a newer release.

Security disclosures

If you found a security issue — in the app, the sandboxing of its analyzer tools, or this website — please use GitHub’s private vulnerability reporting on the repository’s Security tab rather than a public issue, so the fix can ship before the details become public. Reports made that way reach the maintainer directly.

Everything else

For questions about using the app, the README covers install, CLI usage, analyzers, report formats and CI integration — and the CI guide covers pipeline setups. The best unknown-answer detector is still reading an issue thread; search the tracker before opening a new one.