NourForge formats
Checker recognises NourForge Manifest, Legacy SHA256 CHECKSUM REPORT and Enhanced NourForge Portable Verification Data v1 in TXT or CSV form.
NOURFORGE ARCHIVE VERIFY CHECKER · GUIDE
Supported SHA-256 manifest formats
Understand Checker’s automatic format detection and the layouts accepted for whole-file SHA-256 verification.
GNU and BSD formats
Supported established layouts include GNU SHA256SUMS text lines, GNU binary-marker lines and BSD SHA-256 output.
CSV
Two-column CSV can be filename then SHA-256 or SHA-256 then filename. A supported heading may declare the orientation; quoted CSV fields are parsed as CSV rather than split naively.
Delimited text
Checker recognises tab-delimited lists in either orientation, plus filename-pipe-SHA-256 and filename-semicolon-SHA-256 layouts.
Generic lists
Whitespace-separated filename followed by SHA-256 and SHA-256 followed by filename are supported when every meaningful row follows one consistent, unambiguous grammar.
Detection safeguards
Every meaningful data row must match the detected format and orientation. Ambiguous, inconsistent or checksum-like unsupported data is reported instead of being guessed silently.
Candidate filenames
Automatic folder discovery evaluates common TXT, CSV, TSV, SHA256 and SHA256SUM-style files, including a file named SHA256SUMS.
NEED MORE HELP?
Support is available and feedback is welcome.
Tell us where a guide or workflow can be clearer. Open NourForge Archive Verify Checker support →