Trust and verification
The facts a security reviewer asks for first, each one checkable against the public repository, the release assets or the docs.
- License
- Apache 2.0
- Published by
- GLINCKER
-
Signed releases
SHA-256 checksums, a keyless cosign signature and build provenance on every release.
-
No usage telemetry
The product sends none. The code is open so you can check.
-
Private disclosure
Report a vulnerability through GitHub or email, not a public issue.
How releases are built
- The source is public under Apache 2.0 at github.com/glincker/levelrail. There is one edition and no license key.
- Releases are built by a GitHub Actions workflow (
release.yml) in that repository and published as GitHub release assets. - Each release carries
checksums.txt(SHA-256 of every CLI, agent and control plane binary), a keyless cosign signature bundle for it (checksums.txt.sigstore.json), and a GitHub build provenance attestation for the binaries. - Container images are signed keylessly with cosign through GitHub Actions OIDC, so there is no long-lived signing key to steal. Images are built with provenance and an SBOM attached as build attestations.
- Releases cut before signing was added carry no signature bundle.
Verify downloads
install.sh always checks the SHA-256 checksum and refuses to install on a mismatch. It also verifies the cosign signature when cosign is present and the release ships a bundle, and APP_INSTALL_VERIFY=require makes a missing or bad signature abort. To check by hand, use the release assets from the latest GitHub release:
V=v0.1.0 # the release tag
BASE=https://github.com/glincker/levelrail/releases/download/$V
curl -fsSLO $BASE/checksums.txt -O $BASE/checksums.txt.sigstore.json -O $BASE/levelrail-linux-amd64
cosign verify-blob --bundle checksums.txt.sigstore.json \
--certificate-identity-regexp 'https://github.com/glincker/levelrail/\.github/workflows/release\.yml@.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
checksums.txt
sha256sum --check --ignore-missing checksums.txt
gh attestation verify levelrail-linux-amd64 --repo glincker/levelrail To verify a container image:
cosign verify ghcr.io/glincker/levelrail:latest \
--certificate-identity-regexp 'https://github.com/glincker/levelrail/\.github/workflows/release\.yml@.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
Full behavior, including signature pinning after the first verified install, is in the install docs. Asset names live under https://github.com/glincker/levelrail/releases/download/<tag>.
What the product sends over the network
- No usage telemetry. A search of the Go source for analytics, usage reporting and crash reporting libraries finds none, and the code is open so you can check.
- Secrets, metrics and logs stay on your own servers. Each node keeps its own time series and log store.
- The one built-in lookup is a release check against GitHub's releases API. The periodic check runs only if an operator opts in, and the Updates page also queries it when opened. It never applies an update by itself.
- Everything else that leaves your network is something you configure: git providers, an ACME certificate authority, container registries, cloud provider APIs, object storage for backups and your alert channels.
Details are in Privacy and data handling in the docs. How this website handles data is on the website privacy page.
Report a vulnerability
Use the repository's private security reporting on GitHub, or email support@levelrail.com. Please do not open a public issue for a vulnerability. The machine-readable contact is in security.txt. Fixed issues are listed on the security advisories page.
No compliance certification is claimed, and the threat model lists known gaps.