◍ Downloads
Every release binary, with checksums. If you just want it installed, the one-line installers do this for you.
RELEASE-MANIFEST covers the checksums below, the Windows
binaries carry an Authenticode signature, and the macOS binaries oam's
own self-signed one. Verify before running, especially on a machine you
did not build them on.
Binaries
| Platform | File | Size |
|---|---|---|
| macOS · Apple Silicon | oam-aarch64-apple-darwin | 66.0 MB |
| macOS · Intel | oam-x86_64-apple-darwin | 69.5 MB |
| Windows · ARM64 | oam-aarch64-pc-windows-msvc.exe | 67.7 MB |
| Windows · x64 | oam-x86_64-pc-windows-msvc.exe | 74.1 MB |
| Linux · x64 (glibc) | oam-x86_64-unknown-linux-gnu | 75.1 MB |
No linux-arm64 build yet: it compiles, but the V8 startup snapshot cannot be cross-compiled, so it needs a native ARM builder. SHA256SUMS, LICENSE, NOTICE and THIRD_PARTY_LICENSES.md ship with every release, and from v0.18.0 on so do RELEASE-MANIFEST and RELEASE-MANIFEST.sig.
SHA256SUMS (v0.21.1)
98c52c9d2b9976f3310e73a7f0a25ff469e03666539d34d7c83877d414af02d8 *oam-aarch64-apple-darwin
2761255bc25f9d422e89a49e840bc5a0b5baf3e3bf3dac5eb48db80a988fe6bf *oam-aarch64-pc-windows-msvc.exe
5bfbc616050d25260410ec9ed1c37e769e4999a84383c066ba5bf442bec8ba32 *oam-x86_64-apple-darwin
0155da97d588784a21eaf48e49b5412c1624276dbbfa32235681c93040f8523d *oam-x86_64-pc-windows-msvc.exe
91dba01b505f7363901eed764f4838987d5422b3a1a85cd0be976ac4ad0b4122 *oam-x86_64-unknown-linux-gnu
a5b73111e8a412052c51252055a1a3caab857b24f50dd86aaacb2971223f4b2f *LICENSE
094416965923a392f2cbe96d9d938b2f484285d21fe0b03f4831039628aeee24 *NOTICE
30d2713a86a658676869d2bc7dbcde0ef76ead9c98c5c5724ccba8a9de89da4c *THIRD_PARTY_LICENSES.md
Verify
macOS and Linux — check every file the release published:
curl -fsSLO https://github.com/YawLabs/oam/releases/download/v0.21.1/SHA256SUMS
shasum -a 256 -c SHA256SUMS --ignore-missing
Or a single file, compared against the line above:
shasum -a 256 oam-aarch64-apple-darwin
Windows (PowerShell):
Get-FileHash .\oam-aarch64-pc-windows-msvc.exe -Algorithm SHA256 | Format-List
Get-FileHash prints uppercase; the sums above are lowercase.
Compare case-insensitively, or pipe through
.Hash.ToLower().
From v0.18.0 on, also check the release
signature. A checksum proves the bytes match the release page; the
signature proves the sums came from the holder of oam's release key.
macOS and Linux, next to the SHA256SUMS fetched above:
curl -fsSLO https://github.com/YawLabs/oam/releases/download/v0.21.1/RELEASE-MANIFEST
curl -fsSLO https://github.com/YawLabs/oam/releases/download/v0.21.1/RELEASE-MANIFEST.sig
curl -fsSLO https://raw.githubusercontent.com/YawLabs/oam/main/release-keys/allowed_signers
ssh-keygen -Y verify -f allowed_signers -I oam-release-k1 \
-n oam-release -s RELEASE-MANIFEST.sig < RELEASE-MANIFEST
head -2 RELEASE-MANIFEST
tail -n +3 RELEASE-MANIFEST | cmp - SHA256SUMS
The verify should report a good signature from key
SHA256:zB7Aq4Ky/U90VJ4sAEp0e2A65KfQpiyQXJI4FuT2oss, the
fingerprint also published in oam's
SECURITY.md;
the manifest's second line should name the tag you downloaded; and
cmp should print nothing. The
signing post has the
full walkthrough, including Windows and the per-binary signatures.
After downloading
The file is the whole runtime — there is nothing to unpack. On macOS and
Linux mark it executable and put it on your PATH:
chmod +x oam-aarch64-apple-darwin
mv oam-aarch64-apple-darwin ~/.local/bin/oam
oam --version
macOS quarantines files downloaded by a browser, and Gatekeeper will refuse the first run: the macOS binaries are not notarized, and from v0.18.0 on they are signed with oam's own self-signed identity rather than an Apple Developer ID. Verify the download, then clear the attribute:
xattr -d com.apple.quarantine ~/.local/bin/oam
On Windows, the .exe is Authenticode-signed by
“Yaw Labs LLC” from v0.18.0
on. SmartScreen may still show an unrecognized-app screen while that
signature builds reputation.
Installing a specific version
The installers take OAM_VERSION — a release tag, including
the v. Unset, they resolve the latest release.
macOS and Linux:
curl -fsSL https://oamjs.org/install.sh | OAM_VERSION=v0.21.1 sh
The variable has to be on sh, not on curl —
curl is a different process and would not pass it along.
Windows:
$env:OAM_VERSION = "v0.21.1"; irm https://oamjs.org/install.ps1 | iex
Two related knobs: OAM_INSTALL_DIR changes the target
(default ~/.oam/bin, or %LOCALAPPDATA%\oam\bin),
and OAM_INSTALL_BASE points at a mirror instead of GitHub
Releases (it needs OAM_VERSION too, because the signature
is checked against the tag you asked for). Whatever the source, the
installer verifies the release's signed RELEASE-MANIFEST
with release keys built into the script, takes each binary's SHA-256
from it, and refuses a mismatch. For a release before
v0.18.0, which has no manifest, it
checks the published SHA256SUMS against a digest pinned in
the script instead. The signature check needs ssh-keygen
from OpenSSH 8.1 or later; OAM_INSECURE_SKIP_SIGNATURE=1
lets a host without one install, and skips nothing else.
An existing install updates itself with oam self-update.
From v0.18.0 it makes the same checks
itself, with the release keys compiled into the binary; older binaries
re-run this installer.
All releases
Older versions, with notes and their own checksums, are on the releases page.