Skip to main content

Downloads

One release of the public connectors repository, tag vX.Y.Z, ships everything you install to build on Constellation or connect a mission control system: the CLI, the SDKs, the bridges, the plugins and the images. The fleet agent is released on its own and installs from install.constellation.space/agent.

Releases are on the repository's Releases page, with no sign-in. Fetch a whole release with gh, or one file with curl:

VERSION=vX.Y.Z # the release you use
gh release download "$VERSION" --repo constellationhq/connectors --dir "constellation-$VERSION"
curl -fsSLO "https://github.com/constellationhq/connectors/releases/download/$VERSION/constellation-yamcs.jar"

Releases before 1.0 are pre-releases: releases/latest and the latest image tag skip them. Use versioned links and tags.

Release files​

FileWhat it isUsed by
constellation-linux-amd64, constellation-linux-arm64, constellation-darwin-amd64, constellation-darwin-arm64The constellation CLI, one static binary each. Rename it constellation, make it executable, put it on your PATH.Build a connector
constellation_space-<version>-py3-none-any.whlThe Python SDK with the Yamcs and Lattice bridges: pip install ./constellation_space-<version>-py3-none-any.whlPython bridges, constellation bridge run
constellation_space-<version>.tar.gzThe same Python package as source
constellationspace-client-<version>.tgzThe TypeScript SDK: npm install ./constellationspace-client-<version>.tgzTypeScript bridges and apps
yamcs-constellation-<version>.tar.gzconstellation-yamcs.jar and the bridge's compose.yaml and .env.example: everything a Yamcs install needsYamcs
constellation-yamcs.jarThe Yamcs plugin on its own: Constellation's parameters and the Constellation Forecast pageYamcs
yamcs-bridge.pyzThe Yamcs bridge as one file: python3 yamcs-bridge.pyz (Python 3.11 or newer)Yamcs
lattice-bridge.pyzThe Lattice bridge as one file: python3 lattice-bridge.pyz (Python 3.11 or newer)Anduril Lattice
openc3-cosmos-constellation-<version>.gemThe COSMOS pluginOpenC3 COSMOS
constellation-openmct.jsThe Open MCT plugin as one file a page loads with a <script> tagOpen MCT
openmct-constellation-forecast.zipThe same plugin as ES modules, constellation-forecast.js and forecast-view.js, for an Open MCT you buildOpen MCT
<file>.spdx.jsonA software bill of materials (SPDX JSON) for each file aboveYour security review
SHA256SUMSThe SHA-256 checksum of every file in the releaseVerifying
SHA256SUMS.sigstore.jsonThe keyless Sigstore signature over SHA256SUMSVerifying
ImageWhat it is
ghcr.io/constellationhq/yamcs-bridge:<version>The Yamcs bridge, amd64 and arm64, runs as a non-root user, state in /var/lib/constellation
ghcr.io/constellationhq/lattice-bridge:<version>The Lattice bridge, amd64 and arm64, runs as a non-root user, state in /var/lib/constellation

The same release goes to the public registries, from the first public release on:

RegistryName
PyPIconstellation-space
npm@constellationspace/client
RubyGemsopenc3-cosmos-constellation
Maven Centralspace.constellation:constellation-yamcs
Gogithub.com/constellationhq/connectors/cli, tagged cli/vX.Y.Z with each release. Go bridges need no download.

Verify a download​

Every release is signed keyless with Sigstore by the repository's own release workflow, and a release whose signature fails is never published. constellation verify checks SHA256SUMS against that signature, then the files against SHA256SUMS, in one step. It needs cosign:

constellation verify "constellation-$VERSION"
ok SHA256SUMS is signed by the constellationhq/connectors release workflow
ok constellation-yamcs.jar
-- lattice-bridge.pyz (not downloaded)

A file SHA256SUMS lists that you did not download is noted, not failed. verify refuses a release that is not signed, and verifies nothing then.

Without the CLI, use cosign and sha256sum:

cosign verify-blob --bundle SHA256SUMS.sigstore.json \
--certificate-identity-regexp '^https://github\.com/constellationhq/connectors/\.github/workflows/release\.yml@refs/tags/v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?$' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS

The images are signed the same way:

cosign verify ghcr.io/constellationhq/yamcs-bridge:<version> \
--certificate-identity-regexp '^https://github\.com/constellationhq/connectors/\.github/workflows/release\.yml@refs/tags/v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?$' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com

These are the checks constellation verify makes: the signing certificate must name the connectors repository's release.yml workflow, run for a vX.Y.Z tag, issued through GitHub Actions, with the signature in the public Sigstore transparency log. A signature from anywhere else, such as a fork or a branch, fails.

Every file also carries a GitHub build provenance attestation: gh attestation verify <file> -R constellationhq/connectors.

Mirror a release for an air-gapped site​

On a machine with access, fetch and verify the release, then copy the images:

VERSION=vX.Y.Z
gh release download "$VERSION" --repo constellationhq/connectors --dir "constellation-$VERSION"
constellation verify "constellation-$VERSION"

for image in yamcs-bridge lattice-bridge; do
docker pull "ghcr.io/constellationhq/$image:${VERSION#v}"
docker save "ghcr.io/constellationhq/$image:${VERSION#v}" -o "constellation-$VERSION/$image.tar"
done

Carry the folder across, check it again on the inside with sha256sum --ignore-missing -c SHA256SUMS, then:

WhatOn the inside
Imagesdocker load -i yamcs-bridge.tar, then tag and push to your own registry. Or copy registry to registry with skopeo copy or crane copy, which keep the signatures.
Pythonpip install ./constellation_space-<version>-py3-none-any.whl, or upload the wheel to your own package index. The bridges and the SDK need nothing beyond the standard library; the [lattice] extra needs sgp4, so fetch it with pip download sgp4 on the outside.
TypeScriptnpm install ./constellationspace-client-<version>.tgz, or publish the tarball to your own registry. It has no runtime dependencies.
GoRun go mod vendor in your bridge on the outside, and build with the vendor/ folder on the inside.
PluginsCopy the tarball, jar, gem and script as the connector's page says.

Serve the folder as it is, file names unchanged, so SHA256SUMS still matches. A bridge still needs outbound HTTPS to the Constellation API it reads, or to your enterprise API inside the site.