Downloads and checksums
Every export script and the spec that defines them ship as attached assets
on a tagged noblecloak-tools
release. No code-signing is applied — verify the checksum of what you
download against the values below before you run it.
v0.1.0
Release page: github.com/bianoble/noblecloak-tools/releases/tag/v0.1.0
| Asset | SHA-256 |
|---|---|
nc-export.py | 8a84cb79eb9cae576ffad235b19e892e58b1c8e3fbae1b55fd7b99a13da023c1 |
nc-export-entra.ps1 | 92c14cc1924a7d8af925963a0a460313167c96b829bcec9988dc5a23ddd6c896 |
discover-export-format-v1.md | b6957d0c7afd699059bae0135405c42eeb23719bac1b5381e4369519b3bb660d |
A SHA256SUMS.txt sidecar file with the same three values is attached to
the release alongside the assets themselves.
A mismatch between this table and the release page is a trust bug, not a cosmetic one — if you see one, do not run the script; contact support@noblecloak.com.
Verify what you downloaded
macOS / Linux:
shasum -a 256 nc-export.py
shasum -a 256 nc-export-entra.ps1
Windows / PowerShell:
Get-FileHash nc-export-entra.ps1 -Algorithm SHA256
Get-FileHash nc-export.py -Algorithm SHA256
Compare the output against the table above. The release workflow that
produces the published checksums is public, so you can check the method
yourself rather than take it on faith:
.github/workflows/release.yml.