Where to Find Kryptor's Source Code, License, and Support

Updated

Kryptor's source code is hosted on GitHub, the project is licensed under GPLv3, and GitHub is also the place to report bugs, give feedback, ask questions, or request technical support. Security vulnerabilities should be reported according to the project's SECURITY.md file, and other enquiries can go to the author by email.

Source code and license

Item Where to find it Notes
Source code GitHub (linked from the Kryptor site) The site points to GitHub as the canonical location
License Stated on the Kryptor site GPLv3
Documentation index llms.txt on the site Full documentation index; pages are also available as Markdown

The site describes Kryptor as a file encryption and signing tool for Windows, Linux, and macOS, positioned as a leaner, more user-friendly alternative to GPG and a better version of age and Minisign. Its stated use case is protecting files for backups and sharing, with a focus on limiting metadata. It is explicitly not intended as a complete GPG replacement.

Support and contact channels

Use the channel that matches what you need:

  • Bug reports, feedback, questions, technical support — GitHub. This is the project's stated primary channel for all of these.
  • Security vulnerabilities — follow SECURITY.md rather than opening a public issue.
  • Other enquiries — email the author at samuel at samuellucas dot com (the site writes the address this way to avoid scraping; convert it to a normal address before sending).

The site also asks users to follow the project on GitHub to stay up to date, which is the practical way to hear about releases and fixes.

Practical notes before you rely on the project

A few details from the site affect how you use the source and builds:

  • macOS packaging caveat. For macOS (x64 and ARM64), an upstream .NET SDK issue prevents the libsodium library from being bundled into the Kryptor executable. Until it is resolved, you must keep libsodium.dylib (inside the download ZIP) in the same directory as the kryptor file. The site notes the .NET team has not investigated this for over a year, so treat it as a long-term constraint rather than a temporary glitch.
  • Install routes. Pre-built binaries exist for Windows (x64), Linux (x64 and ARM64), and macOS (x64 and ARM64), each with a Kryptor signature and SHA-256 digest. Package managers include Chocolatey and Scoop on Windows, AUR on Arch Linux (kryptor from source or kryptor-bin for the published binary), and nix-shell -p kryptor on NixOS. Homebrew on macOS is listed as "help wanted," so don't assume a Homebrew formula exists.
  • Verification. The site directs you to its Installation page for instructions on verifying signatures and digests. If you are building from source or using a package manager, checking the signature and SHA-256 against the published values is the step that ties a download back to the project.
  • Project scale. The author describes himself as a student and asks for donations (PayPal, Monero). That context is relevant to expectations about support responsiveness and long-term maintenance.

What this means for choosing Kryptor

If your priority is an auditable, simply scoped encryption and signing tool and you are comfortable with GPLv3 terms and GitHub-based support, the source, license, and contact paths above are all you need to get started. If you need a vendor with formal support contracts, or you require a drop-in GPG replacement, Kryptor's own documentation says it is not aiming for that role.