generated: '2026-08-29' method: searched source: >- Registry metadata endpoints (registry.npmjs.org, pypi.org/pypi, crates.io/api/v1, search.maven.org, hackage.haskell.org, hub.docker.com/v2) plus https://github.com/swift-nav/libsbp and https://github.com/swift-nav/sora-device-client name: Swift Navigation client libraries and distributions note: >- Swift Navigation's first-party client libraries are all generated from one source: the libsbp repository, which holds the machine-readable Swift Binary Protocol specification and emits bindings for C, Python, Rust, Java, JavaScript and Haskell from it. Every language binding therefore carries the SAME version number, released together. Verified against each registry's own metadata endpoint on 2026-08-29. packages: - name: sbp registry: pypi url: https://pypi.org/project/sbp/ language: python official: true version: 6.5.1 published: '2026-07-08' source_code: https://github.com/swift-nav/libsbp note: Python bindings for Swift Binary Protocol; also ships the sbp2json tool. - name: sbp registry: npm url: https://www.npmjs.com/package/sbp language: javascript official: true version: 6.5.1 published: '2026-07-08' source_code: https://github.com/swift-nav/libsbp note: >- Publisher on the npm record is dev@swift-nav.com, which is how first-party ownership was confirmed — the package name "sbp" is generic and there is an unrelated npm package family using similar names. - name: sbp registry: crates.io url: https://crates.io/crates/sbp language: rust official: true version: 6.5.1 published: '2026-07-08' source_code: https://github.com/swift-nav/libsbp - name: sbp registry: hackage url: https://hackage.haskell.org/package/sbp language: haskell official: true version: 6.5.1 published: '2026-07-08' source_code: https://github.com/swift-nav/libsbp note: Version read from hackage.haskell.org/package/sbp/preferred; 47 published versions. - name: com.swiftnav:sbp registry: maven-central url: https://central.sonatype.com/artifact/com.swiftnav/sbp language: java official: true version: 5.0.7 published: '2024-03-27' source_code: https://github.com/swift-nav/libsbp note: >- DECAY SIGNAL. The Java binding is TWO MAJOR-MINOR generations behind its five sibling bindings (5.0.7 / 2024-03-27 vs 6.5.1 / 2026-07-08 for Python, npm, Rust and Haskell). All six are generated from the same libsbp spec, so a Java consumer is missing every SBP message added since March 2024 — including the integrity, signing and MessagingQueue subsystems added in 6.x. - name: sora-device-client registry: pypi url: https://pypi.org/project/sora-device-client/ language: python official: true version: 1.1.0 published: '2023-04-17' source_code: https://github.com/swift-nav/sora-device-client note: >- DECAY SIGNAL. Last release 2023-04-17. The gRPC service it talks to (https://grpc.sora.swiftnav.com) now presents a "Kubernetes Ingress Controller Fake Certificate" rather than a valid public certificate, and the Sora introduction article it links to redirect-loops. Treat the Sora surface as retired. - name: swiftnav/libsbp-build registry: dockerhub url: https://hub.docker.com/r/swiftnav/libsbp-build language: multi official: true version: null published: '2026-07-05' note: >- Build/toolchain image for regenerating the SBP bindings, not a consumer SDK. Tags are not semver-pinned to the libsbp release, so version is recorded null; the date is the registry's last_updated. absent: - registry: rubygems checked: '2026-08-29' status: 404 note: https://rubygems.org/api/v1/gems/sbp.json returns 404 — no Ruby binding published. - registry: nuget checked: '2026-08-29' note: No first-party .NET binding is generated by libsbp and none was found. - registry: pkg.go.dev checked: '2026-08-29' note: >- libsbp does not emit a Go binding. swift-nav publishes Go tooling (rgeo, carvel-ytt forks) but no Go SBP client.