rskey distributes pre-built binaries for all major platforms. You can download a release archive directly from GitHub, install aDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/rstudio/rskey/llms.txt
Use this file to discover all available pages before exploring further.
.deb or .rpm package on Linux, or build from source using the Go toolchain. No license key or product installation is required.
Binary releases
Pre-built binaries are available on the rskey GitHub releases page for the following platforms and architectures:| Platform | Architectures | Format |
|---|---|---|
| Linux | amd64, arm64 | .tar.gz |
| macOS | amd64, arm64 | .tar.gz |
| Windows | amd64, arm64 | .zip |
.deb and .rpm packages from the same releases page. These packages place the rskey binary in your PATH and include the LICENSE, README.md, and NOTICE.md files under /usr/share/doc/rskey/.
To install from an archive:
.deb package:
.rpm package:
Install with Go
If you have Go 1.24 or later installed, you can build and install rskey directly from source:rskey binary in $GOPATH/bin (typically ~/go/bin). Make sure that directory is in your PATH.
Verify binary signatures
All rskey binary releases are signed with Sigstore using Cosign’s keyless mode. Keyless signing uses OpenID Connect tokens issued by GitHub Actions for this repository and short-lived ephemeral certificates instead of long-lived private keys, which means there is no signing key to manage or rotate. To verify a release archive, install thecosign CLI and run:
.sig file on the releases page. Download both the archive and its .sig file before running cosign verify-blob. If the signature is valid, cosign prints a confirmation message and exits with code 0.
rskey does not require a Posit product license, a Posit account, or any product installation. You can generate keys and encrypt secrets on any machine where rskey is installed, regardless of whether Posit Connect, Package Manager, or Workbench is present.