Folder hash manifest

Hash every file you drop and produce a manifest in the same `<hex> <name>` format `shasum`/`sha1sum`/`md5sum` print, for spot-checking against the real tool.

Folder hash manifest hashes every dropped file using sha256, sha1 or md5 from hash-wasm, printing one line per file in the same <hex> <name> shape shasum, sha1sum and md5sum use. Files hash in drop order, each line reported as its progress finishes. It only hashes the bytes given, so it cannot say whether they match a remote copy.

Questions

What hash algorithms are available?

sha256, sha1 and md5, all computed with hash-wasm.

What format is the manifest?

One line per file, <hex digest> <file name>, the exact format shasum, sha1sum and md5sum print.

What order are files listed in?

The order you dropped them in; the manifest keeps that order rather than sorting by name or size.

Can I verify this against the real shasum command?

Yes, the output is meant to be diffed or spot-checked directly against shasum, sha1sum or md5sum output on the same files.

Does it verify the files against anything else?

No, it only hashes the bytes it was given; it cannot compare them against a remote copy or a known-good manifest.

Related Forensics tools

n→nDetect file typeIdentify a file by its magic bytes, not its extension;n→nExtract stringsPull runs of printable text out of any binary file: the classic first look at an unknown file.n→nExtract embedded filesCarve out the bytes starting at each detected file signature, up to the next signature or end of file.n→nScan for embedded/appended filesScan every offset for known file signatures: finds a file hidden or appended inside another, e.g. a ZIP tacked onto a JPEG. A match means "signature found here", not "a file was deliberately hidden".1→1File tree from archiveList the paths, sizes and structure inside a ZIP or TAR archive, without extracting anything.n→nTrailing dataFind and carve out bytes appended after a PNG/JPEG/PDF/ZIP/GIF's real end marker, a common place to smuggle a second payload.n→nPolyglot detectCheck whether a file carries more than one valid format signature, at offset 0 or buried inside, the hallmark of a polyglot file.n→nMagic decodeTry base64, base32, hex, URL-encoding, ROT13/47 and single-byte XOR against a string and rank the results by how much they read like real text.