ZIP - All Members Stored
A ZIP whose every member uses compression method 0 (stored). Its twin holds byte-identical content under the other method, so an extractor, a size estimator, or a repacking pipeline can be compared on the same payload with only the storage method changed.
- README.txt
- notes.md
- records.csv
Specifications
- Seed
- 20260807
- Compression Method
- 0 (stored)
- Members
- 3
- Uncompressed Bytes
- 589
- Twin
- identical content, the other method
Testing contract
Expected to pass- Scenario
- Extract both members of the stored/deflate twin pair and compare the payloads and the reported per-member compression method.
- Expected result
- Every extracted member is byte-identical across the pair, and this archive reports method 0 (stored) for all 3 members.
What is a .zip file?
ZIP is a widely supported archive format that bundles multiple files and directories into one container, typically with per-file DEFLATE compression and a central directory index. It supports random access to individual entries without decompressing the whole archive. It underlies many document formats such as DOCX and EPUB.
How to use this file
Use an example ZIP to test archive extraction, central-directory parsing, per-entry decompression, and protection against path-traversal (zip-slip) during unpacking.
How to use this file for testing
“ZIP - All Members Stored” is a deterministic Novus Examples fixture for Conversion testing, Compression testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: seed 20260807. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Archive fixtures are documented down to their member list (shown on this page) and are deliberately safe — no zip bombs, executables, or hidden payloads. Test extractors against nested, unicode, empty, and encrypted variants.
Code examples
unzip -l method-stored.zip # list members
unzip method-stored.zip -d out/ # extractRelated files
- zipConvert v2 Archive-Media ZIP ControlExisting-format ZIP/TXT media control combining a plain README and a WebVTT sidecar for nested media extraction checks Stable P8 artifact p8-convert-legacy-archive-media-control.
- cabConvert v2 CAB Stored ControlValid single-file Microsoft Cabinet using uncompressed CFDATA for bounded legacy extraction tests Stable P8 artifact p8-convert-legacy-cab.
- tar.bz2Convert v2 Canonical TAR.BZ2Canonical compound-suffix source for the same deterministic bzip2-compressed TAR member set Stable P8 artifact p8-convert-tar-bz2.
- tar.xzConvert v2 Canonical TAR.XZCanonical compound-suffix source for the same deterministic XZ-compressed TAR member set Stable P8 artifact p8-convert-tar-xz.
- rarConvert v2 RAR4 Stored ControlValid RAR4 archive with two stored members and fixed metadata for legacy extraction tests Stable P8 artifact p8-convert-legacy-rar.
- tar.zstConvert v2 TAR.ZST Source 01Valid Zstandard-compressed TAR source 01 with 2 safe members for compound-suffix detection and extraction Stable P8 artifact p8-convert-tar-zst-01.
Generated by generation/archives_p7.py. Free for any use, no attribution required — license.