Skip to content
Novus Examples
tar.zst157 B

Convert v2 TAR.ZST Source 01

Valid Zstandard-compressed TAR source 01 with 2 safe members for compound-suffix detection and extraction Stable P8 artifact p8-convert-tar-zst-01.

Archive contents — 2 entriestar.zst
  • README.txt
  • points.csv

Specifications

Members
2
Delivery Mode
download-only
Compression
Zstandard
Validity
valid
Provider
converter-v2
Provenance
Synthetic deterministic P8 fixture generated by generation/p8_content.py; seed namespace 2026082300
Fixture Reserve
convert-v2

Testing contract

Expected to pass
Scenario
Decompress the Zstandard frame, parse the TAR stream, and list member paths without writing outside a temporary directory.
Expected result
The frame and TAR checksums validate and extraction yields exactly README.txt, data/points.csv with no absolute or parent-segment path.

What is a .tar.zst file?

TAR.ZST combines a POSIX tar member stream with Zstandard compression. The outer Zstandard frame must be decompressed before 512-byte tar headers, file payloads, padding, checksums, and end blocks can be interpreted; concatenated frames and long-path extensions make robust implementations treat compression and archive parsing as separate stages.

How to use this file

Use an example .tar.zst file to test streaming decompression, tar checksum and member parsing, path-traversal rejection, bounded expansion, deterministic member manifests, and clean failure on a deliberately truncated Zstandard frame.

How to use this file for testing

“Convert v2 TAR.ZST Source 01” 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: TAR.ZST · 157 bytes. 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.

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