Skip to content
Novus Examples
zip769 B

ZIP - Directories Implied by Member Paths

The same three-directory tree with no directory records at all — the parents exist only as path components inside member names. Extractors that create directories only when they see a directory record fail on this shape, which is what most command-line ZIP writers produce.

Archive contents — 3 entrieszip
  • README.txt
  • main.txt
  • records.csv

Specifications

Seed
20260807
Directory Records
0
File Records
3
Directory Convention
no directory members; parents exist only inside member paths

Testing contract

Expected to pass
Scenario
Extract the archive into an empty directory without pre-creating any parents.
Expected result
project/, project/src/ and project/data/ are created on demand and all 3 files land inside them; nothing is written to the extraction root.

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 - Directories Implied by Member Paths” is a deterministic Novus Examples fixture for Conversion 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 directories-implied.zip     # list members
unzip directories-implied.zip -d out/  # extract

Generated by generation/archives_p7.py. Free for any use, no attribution required — license.