Janus sits between Claude Code and the Anthropic API, so it sees your credentials, prompts, and code. A problem that could expose any of them, or let something reach a machine it shouldn't, is a security problem.
Report it privately: on the repository's Security tab, choose Report a vulnerability (https://github.com/risadams/Janus/security/advisories/new). Please don't open a public issue for it.
Say what you found, how to reproduce it, and which version (janus version)
you ran. Leave out real credentials and captures.
The threat model sets out what Janus is trusted with, who it defends against, and the risks it accepts. A report is most useful when it shows one of those defences failing, or a risk the threat model doesn't account for.
Each release's checksums.txt is signed with the Janus release key, and
the signature is checksums.txt.sig beside it. The keys are listed, the
newest first, in
internal/update/release-keys.txt;
take the key from the repository rather than from a release, which is
the thing being checked. ADR-003 says
why it is done this way and how keys are rotated.
With OpenSSL 3 or later, and the key as key:
key='<the newest line of release-keys.txt>'
curl -LO "${url%/*}/checksums.txt.sig" # url as in the README
{ printf '\060\052\060\005\006\003\053\145\160\003\041\000'; printf '%s' "$key" | base64 -d; } > janus-release.der
openssl pkeyutl -verify -pubin -keyform DER -inkey janus-release.der \
-rawin -in checksums.txt -sigfile checksums.txt.sigIt prints Signature Verified Successfully, or fails. The first printf
is the fixed header that turns a bare ed25519 key into the DER form
OpenSSL reads. Then check the archive against the sums with shasum -a 256 -c checksums.txt --ignore-missing, as in the README. The release
workflow runs these same commands on every build, so they work as
written.
gh attestation verify <archive> --repo risadams/Janus checks a stronger
claim, that this repository's workflow built the archive from the tagged
commit, if you have the GitHub CLI. From v0.9.0-rc.17, the attestation is
also published with the release, as janus_<version>.intoto.jsonl; add
--bundle janus_<version>.intoto.jsonl to check against that file rather
than asking GitHub for it.
Each archive also has an SBOM beside it, <archive name>.cdx.json in
CycloneDX form: the Go toolchain, the standard library, and Janus's own
packages, which are all a release contains, with the platform it was
built for. Its attestation binds it to the archive; check it with
gh attestation verify <archive> --repo risadams/Janus --predicate-type https://cyclonedx.org/bom. The SBOMs are not in checksums.txt: they
name Janus's version as Git describes the checkout, so a rebuild from a
fresh clone writes them with a different version string.
A release can be rebuilt from its tag, byte for byte, on any machine with
Git, Bash, and Go 1.21 or later, which fetches the exact toolchain named
in go.mod by itself:
git clone --branch v0.9.0-rc.13 https://github.com/risadams/Janus.git
cd Janus
scripts/release.sh v0.9.0-rc.13
diff <(curl -sL https://github.com/risadams/Janus/releases/download/v0.9.0-rc.13/checksums.txt) dist/checksums.txtNo output from diff means every archive is the one published. From
the first release after v0.9.0-rc.16 the darwin archives hold binaries
signed with a Developer ID and notarized by Apple, a signature a rebuild
cannot make, so diff shows their two lines. Compare a rebuild with
checksums-before-codesign.txt instead, which the release also carries:
the sums of the archives as built, before the darwin binaries were
signed. It is not signed with the release key; what a download is
checked against is still checksums.txt. The
build dates each file at the tagged commit's time and records no paths,
build ID, or anything of the machine it ran on; on Windows, run it from
Git Bash. The release workflow rebuilds every release this way on macOS
before publishing it, and refuses to publish one that differs.
Releases before v0.9.0-rc.14 were not built this way and do not rebuild the same.
Janus is in pre-release. Fixes go into the next release candidate; there are no backports.