MySetup scan scripts v0.2.0

Version 0.2.0 of the MySetup scan scripts. Each prints a text report of your computer's hardware: the computer's own model,
processor, graphics, motherboard, memory and storage. You read it, then paste it into the Hardware section of your build on
MySetup, where you review every part before anything is saved. Parts from a pasted report are marked
"Detected" at most; the app (app-v0.2.0) can send its report with a code, which can make them Verified.

The scripts only read. They use no network, write no files, install nothing and do not ask for root unless you say so.

New since 0.1.0: the report names the computer itself, as its firmware does (system.vendor, model, family, version, sku
and chassis: a laptop's or a prebuilt's maker and model, and whether it is a desktop, a laptop or a server), on a physical computer
only. Its serial number, UUID and asset tag are never read, and a built computer's placeholders ("System Product Name") are left
out. MySetup's review shows it as a line of its own.

Files

File	For
mysetup-scan.sh	Linux, macOS, the BSDs and other Unix-like systems: sh mysetup-scan.sh
mysetup-scan.ps1	Windows, in PowerShell: powershell -ExecutionPolicy Bypass -File .\mysetup-scan.ps1
SHA256SUMS	Checksums of both

MySetup's build page serves the same two files, with the same checksums.

Check a download

Compare it with the checksums:

sha256sum -c SHA256SUMS --ignore-missing

Or check GitHub's attestation, which records that the file was built from this repository at this tag:

gh attestation verify mysetup-scan.sh --repo eddinn/mysetup-scanner

The scripts are not code-signed. Windows blocks unsigned scripts from the internet by default; -ExecutionPolicy Bypass lifts that
for one run and changes no setting.

Where it has been tested

Tested on real machines: Windows x86-64 (PowerShell 5.1, without admin rights) and Linux x86-64 with systemd (Debian 13, without
root). On other systems the scripts run, but say "untested on this system", and the report says tested=no: please check such a
report before you paste it, and tell us how it went. In a virtual machine or a container a report says so; inside WSL the script
sends you to the Windows script.

The scripts also ran cleanly on GitHub's Linux, Windows and macOS runners and in containers of Alpine, Debian, Ubuntu, Fedora,
Rocky, Arch, openSUSE and Void. That shows they run there and print a valid report, not that real hardware reads correctly.

What a report never contains

Usernames, hostnames, IP or MAC addresses, motherboard or system UUIDs, machine GUIDs, Windows SIDs, product keys, serial numbers of
the computer, its chassis or any part, asset tags, file paths, file names, network names or other software. The report format is in
docs/report-format.md.

Licence: Apache-2.0.