Skip to content

Downloads

Nebo release resources are available on GitHub. This page links to their records for inspection; it does not certify a current installation or offer a recommended SDK download.

Reference Role on this site Official record
Nebo 1.0.0 · 14 August 2026 Historical release 1.0.0 release
neboc 1.0.1 · 28 August 2026 public release Version reported by the exact local hello compiler; public archive identity is separate 1.0.1 release
Nebo 1.1.0 · 12 September 2026 Public release; not the compiler tested by this site 1.1.0 release

Release records and asset names were checked on 2 November 2026. Language Edition 1.0 and compiler release 1.1.0 are different version axes.

The release lists nebo-1.0.0-source.tar, nebo-1.0.0-sdk-linux-x86_64.tar, nebo-1.0.0-docs-offline.tar, NEBO-1.0.0-SHA256SUMS and VERIFY.md, among its uploaded assets. GitHub’s automatically generated source archives are separate files. Do not assume they match the uploaded source archive byte for byte.

  1. Open the official release record for the version you selected.
  2. Read its VERIFY.md. Download the chosen archive and the checksum manifest from that same record into a new directory.
  3. On a system with sha256sum, compute the archive’s digest. For the historical SDK filename:
Terminal window
sha256sum nebo-1.0.0-sdk-linux-x86_64.tar
  1. Compare all 64 hexadecimal characters with the matching filename’s entry in NEBO-1.0.0-SHA256SUMS. A mismatch means stop and investigate; do not execute the archive’s contents.

If you downloaded every file named in the manifest into that directory, you can also run:

Terminal window
sha256sum -c NEBO-1.0.0-SHA256SUMS

Missing files are reported as failures, not silently verified. For 1.1.0, use its own SHA256SUMS and filenames instead. These commands check downloaded files; they are not an installation recipe.

The recorded local 1.0.1 SDK archive has digest 6a239a43e8054d85b59a1140d3576e5f0048660754f295647dcd1b2fc92b3da8. GitHub’s 1.0.1 SDK asset metadata currently reports 3060daf1561429c7f65c596258b8b56df26aa2ba0074c464df02702c98732928. The archives therefore have different identities; this comparison does not establish whether their compiler members match.

See installation limits and reproducibility before drawing a compatibility or provenance conclusion.