Know what you can install before you integrate.
Package availability, source availability, and version compatibility are different promises. This page states each one separately for the Honua SDKs. For Esri REST operation coverage and desktop-client workflows, see the Esri → Honua compatibility matrix.
What the table establishes. It is generated from the deployed sdk-availability.v1.json snapshot and checked against public package registries in CI. A source repository or tag alone does not make a package publicly installable.
Current SDK availability
JavaScript / TypeScript and Python have public packages today. .NET is available from source. Use the versions and install commands below.
| SDK | Availability | Published version | Install path | Compatibility boundary |
|---|---|---|---|---|
JavaScript / TypeScript@honua/sdk-js | Public prerelease / Preview support | 0.1.7-beta.0 | npm install @honua/sdk-js@0.1.7-beta.0 | The published SDK checks the server capability contract. No broader version window is published yet. |
.NETHonua.Sdk | Available from source | Not published | Use the source ↗ | Use the source repository; no public NuGet package is published. |
Pythonhonua-sdk | Public package / Preview support | 0.1.11 | pip install honua-sdk==0.1.11 | The public package targets Python 3.11 or newer. No broader supported server-version window is published yet. |
JavaScript migration companions. @honua/sdk-esri-compat@0.1.7-beta.0 — ArcGIS-shaped JavaScript compatibility layer; @honua/honua-migrate@0.1.3-beta.0 — JavaScript scanner, codemod, and parity-report CLI.
Verified public package state from sdk-availability.v1.json — checked 2026-08-20.
No general version window is published yet. Repository tags and the ArcGIS-compatible currentVersion returned by /rest/info do not establish SDK support. A version window becomes public only when released packages and cross-version evidence exist.
Check the Honua capability contract
Honua SDKs inspect GET /api/v1/admin/capabilities. The response reports the Honua server version, release channel, control-plane API version, metadata schemas, and feature flags used for compatibility decisions.
curl -sS -H "X-API-Key: $HONUA_API_KEY" \
"$HONUA_URL/api/v1/admin/capabilities" | jq '.data.compatibility'/rest/info is intentionally an Esri-compatible discovery endpoint. Its currentVersion value describes that protocol surface; it is not the Honua release version.
Third-party desktop clients (ArcGIS Pro, QGIS)
Third-party desktop clients are tracked as operation-level evidence, because they consume Honua through protocol surfaces rather than a Honua-versioned client library.
| Client | How it consumes Honua | Compatibility source of truth |
|---|---|---|
| ArcGIS Pro / ArcPy | GeoServices REST and supported OGC surfaces | Esri → Honua compatibility matrix and the public operation parity matrix ↗ |
| QGIS | OGC API Features, WMS, WFS, and WMTS | Compatibility and the public client limitations ↗ |
Server-version windows for desktop clients are intentionally not asserted here. Their supported workflows are scoped by operations and current public source and test evidence.
How availability is verified
Honua lists a package as publicly installable only when its registry endpoint resolves. A supported version window requires released SDK and server artifacts plus recorded cross-version evidence. CI checks the generated table and registry state independently.