From 1.3.0 Hash Tool is in maintenance mode. What it accepts is written down once, in CONTRIBUTING.md ("Project
status"): security fixes (high/critical vulnerabilities in .NET or a dependency get a prompt release), dependency and
.NET updates, bug and UI/UX fixes, accessibility, translation fixes, and hash algorithms on real demand; no new
features unless truly necessary.
- README: maintenance, Qodana and .NET 10 LTS badges and a "Project status" section.
- CONTRIBUTING: the policy, the issue forms, and the hash algorithm candidates (BLAKE2b-512, SHA3-256/512, CRC-32C)
with what each would take; ARCHITECTURE: a checklist for adding an algorithm.
- Issue forms: the feature request form is replaced by "Hash algorithm request" and "Translation problem"; feature
ideas go to Discussions (Ideas). The accessibility form gives the email address for people who cannot use GitHub.
- Pull request template: the kinds of change that are accepted.
- SECURITY: 1.3.x supported, the security commitment during maintenance, Qodana among the checks.
- CLAUDE.md: the project status for agents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.5 KiB
Security Policy for HashTool
Last updated: November 2026
HashTool is a free, open-source desktop application built with C# (.NET 10) and Avalonia UI. It processes files locally, has no server components, and only goes online to check GitHub for updates.
Supported Versions
Security fixes are released for the latest minor version only. Installed and portable copies update themselves, so please stay on the newest release.
| Version | Supported |
|---|---|
| 1.3.x | ✅ |
| < 1.3 | ❌ |
Hash Tool is in maintenance mode (see CONTRIBUTING.md), which does not change this: vulnerabilities rated high or critical in the .NET runtime or a dependency, and other serious security problems, get a new release as soon as practical.
How releases are protected
- Releases are built, tested and published by GitHub Actions from the
mainbranch; every release includesSHA256SUMS, CycloneDX SBOMs and build provenance attestations (gh attestation verify <file> --repo poli0981/HashTool). - Every pull request is checked for vulnerable NuGet packages, licences, leaked secrets and unsafe workflow patterns, in addition to CodeQL, Qodana, SonarCloud and OpenSSF Scorecard.
- The apps are not code-signed yet, so Windows SmartScreen and macOS Gatekeeper may warn when they are first opened.
Reporting a Vulnerability
If you discover a potential security vulnerability, please report it responsibly:
- Do not open a public issue — this prevents malicious exploitation.
- Use one of the following methods:
Please include:
- Detailed description of the vulnerability
- Steps to reproduce
- Potential impact
What to Expect
- I will acknowledge receipt within 48 hours (if possible).
- I'll investigate and respond with next steps (accept/decline, timeline for fix).
- If accepted, a fix will be released as soon as practical, and you'll be credited in the release notes (unless you prefer anonymity).
- If declined, I'll explain why.
Thank you for helping keep HashTool secure! 🛡️
© 2026 poli0981. All rights reserved.