Archive integrity test
Check that a ZIP archive's contents can actually be read, member by member.
Working…
Questions people ask
- What does "verified" actually mean here?
- Every non-directory member was decompressed end to end and the runtime checked its stored CRC-32 and declared sizes while reading. Nothing was extracted to disk: the contents are read and discarded, so your archive's data is never written anywhere.
- What if the archive is too big or too hostile?
- The pass runs inside fixed caps: 4096 members, 128 MiB of declared payload per member and 512 MiB in total. Hitting a cap stops the pass and the verdict becomes PARTIAL with a note saying exactly how far it got. An archive the tool could not finish checking is never reported as verified.
- What about encrypted or unusual-compression members?
- Password-protected members are classed (their names and sizes are read) but never decrypted and never CRC-checked, so an archive containing them is honest about it: the verdict notes members whose contents could not be checked. The same goes for members using a compression method this runtime cannot decode.
- What do damaged members look like?
- A member whose stored data fails the CRC or disagrees with its declared size is marked damaged by name, with the reason captured in the report. The first finding is quoted verbatim and bounded, to keep hostile content out of the page.