Public release history across desktop and CLI targets.
Fast, signed downloads for desktop apps and CLI tools
Jumping Crab is the official distribution portal for cross-platform releases, verified packages, and developer builds. Download stable versions, preview beta updates, or test nightly artifacts with published checksums and transparent release notes.
Release snapshot
Current distribution state for public channels, verification, and build delivery.
Production-ready builds with predictable updates and verification metadata.
Download stableEarly access channel for users who want fixes and features before stable rollout.
Explore betaBuilt from the integration branch for validation, CI checks, and compatibility testing.
Review nightlyChecksums and signature references are published alongside public release assets.
Verification guidePlatform downloads
Official builds for major desktop environments and automation workflows.
Installer and portable packages for x64 systems.
Signed builds for Apple Silicon and Intel.
AppImage, tar.gz, and distro-friendly packages.
Minimal binaries for scripting, automation, and deployment.
Release channels
Choose the update stream that matches your deployment tolerance and testing workflow.
Recommended for most users, team rollouts, and systems that need predictable upgrades.
- Update frequencyScheduled minor releases
- AudienceGeneral users and self-hosters
- VerificationChecksums and signature references
Improved package verification, mirror fallback behavior, and packaged CLI release notes.
- Package targets12 public artifacts
- MirrorsNorth America · Europe · APAC
- StatusOperational
Use stable when you need a verified package path, archival visibility, and conservative update behavior.
- DesktopInstaller + portable options
- CLIVersioned binary archives
- Archive retentionPrevious releases available
For testers and maintainers who want early visibility into release candidates and platform changes.
- Update frequencyAs candidate builds are prepared
- AudiencePower users and testers
- VerificationPublished checksums
Includes the new release channel API, cleaner mirror metadata, and package verification refinement.
- Package targets8 preview artifacts
- DocsBeta notes included
- Intended usePreview and validation
Use beta when you want a release candidate path without moving all the way to nightly artifacts.
- DesktopPreview installers available
- CLISemver-tagged beta builds
- Archive retentionPreserved until stable merge
Built from the latest integration branch for compatibility checks, automation tests, and integration work.
- Update frequencyContinuous / daily cadence
- AudienceMaintainers and CI users
- VerificationChecksums published
Incremental CLI improvements, updated download manifest behavior, and release metadata fixes.
- Package targets6 integration artifacts
- RetentionRolling nightly archive
- Ideal forValidation and issue reproduction
Use nightly when you need the newest artifact shape, latest fixes, or reproducible test input.
- DesktopLimited preview builds
- CLIPrimary nightly surface
- Risk profileNot recommended for most users
Recent releases
Recent changes across stable, beta, and nightly channels.
Expanded release metadata, more consistent checksum publishing, and better mirrored asset selection for public downloads.
Refined the packaging workflow for notarized desktop artifacts and improved release-note parity between desktop and CLI packages.
Reduced package discovery time for Linux artifacts and simplified archive metadata for AppImage, tar.gz, and deb outputs.
Introduced clearer beta metadata for downstream integrations and improved release channel differentiation in manifests.
Polished binary naming for arm64 targets, improved archive manifest generation, and tightened checksum output formatting.
Package verification
Verify every package before installation. All public release artifacts include SHA256 checksums, version metadata, and signature references.
Verification metadata is published with public assets so users can validate package integrity before install or distribution.
Docs and quick start
Jumping Crab is a download portal with release workflows, package guidance, and verification policy in one place.
Install the desktop utility, select a release channel, and verify your first public artifact.
Open quick startPlatform-specific setup for Windows, macOS, Linux, and minimal CLI environments.
Read install docsUnderstand build promotion, archive retention, and verification expectations for public packages.
Explore release docsMirrors and delivery infrastructure
Global delivery with mirrored release assets, cached package paths, and automatic fallback routing.
Serves stable public artifacts with cached metadata and fallback-aware delivery paths.
Optimized for desktop installers, CLI archives, and consistent release manifest delivery.
Handles package replication and public release history access for cross-region downloads.
Maintains package availability across mirrored endpoints during transient path or cache issues.
Built in the open
Release metadata, documentation updates, and packaging changes are maintained as part of an open development workflow.
Moderate contributor count that fits an actively maintained open-source distribution portal.
Historical versions remain visible for download, comparison, and rollback workflows.
Desktop installers, portable builds, package archives, and automation-friendly CLI artifacts.
Release notes, documentation changes, and issue tracking follow a visible maintenance rhythm.
FAQ
Common questions about release channels, verification, and package availability.
Stable is recommended for most users. Beta and nightly are intended for preview and testing workflows.
Public release artifacts include checksum metadata and signature references so packages can be validated before installation.
Yes. Portable builds are available for selected Windows and CLI targets alongside installer and archive formats.
Previous releases remain available through the public release archive and tagged release history.
Download the published checksum file for the release, compare it against your package, and review the verification guide for your platform.
Yes. Documentation, release notes, and project workflows follow an open development model with public release metadata.