If you discover a security vulnerability in this project, do not open a public issue.
Please report it privately via one of:
- GitHub Security Advisories: Report a vulnerability
- Email: security@mosspiglet.dev
We will acknowledge receipt within 48 hours and provide a timeline for a fix.
This policy covers the mosskeys-cli workspace:
mosskeys-core: the write-API client, config/credential handling, and local BYOK checkpoint signingmosskeys-cli: themosskeysbinary (clap commands, output)
The cryptographic core lives in metamorphic-crypto
and metamorphic-log; report
issues in the primitives there.
| Version | Supported |
|---|---|
| 0.1.x | Yes |
| < 0.1 | No |
- Zero-knowledge by construction: the CLI transmits only already-public key material and client-signed checkpoint notes.
- BYOK: the checkpoint signing key is read locally at sign time. It is never copied into config, never logged, and never sent to the server. The server only verifies.
- Credentials: the bearer token is stored
0600or read fromMOSSKEYS_TOKEN, and is redacted in all output. - Supply chain: releases are built
--locked, scanned withcargo audit, ship a CycloneDX SBOM andSHA512SUMS, and are signed with keyless cosign plus a SLSA build-provenance attestation. See RELEASING.md to verify a download.