Fanbase v2026.11.03

Changes since https://github.com/fandango-fuzzer/fanbase/tree/v2026.10.26

Added

• cbor/cbor 1.0 — CBOR data items of every major type in preferred serialization, with common tags (dates, bignums, decimal fractions, embedded CBOR, URIs, UUIDs)
• cbor/cbor-boundary 1.0 — CBOR data items at the edges of well-formedness: overlong heads, the largest arguments, every length width, indefinite lengths, all simple values and float specials
• cbor/cbor-tags 1.0 — CBOR items built around the registered tags, each with content valid for it (dates, bignums, rationals, regular expressions, UUIDs, IP addresses, sets and more)
• json/json 1.0 — JSON texts of objects, arrays and scalars nested up to three levels (twelve along one branch), with every string escape and the whole number syntax
• json/json-boundary 1.0 — JSON texts at the edges of what parsers agree on: numbers past double and 64-bit precision, lone surrogates, repeated keys, long strings and deep nesting
• xml/xml 1.0 — XML documents with a declaration, comments, processing instructions, a DOCTYPE with an internal subset of declarations, and nesting elements with attributes, text, CDATA and references
• xml/xml-boundary 1.0 — XML documents at the edges of well-formedness: both versions and quote styles, external identifiers, character references to the ends of the ranges, namespaces, unusual names and white space
• xml/xml-valid 1.0 — XML documents of which those with a DOCTYPE are valid against it, with every kind of declaration, namespaces, the xml: attributes and elements twelve deep

Fanbase v2026.10.26

Changes since https://github.com/fandango-fuzzer/fanbase/tree/v2026.10.20

Added

• 7z/7z 1.0 — 7z archives of one file stored with the Copy coder, with the header's offset, size and CRCs (no compression, one file)
• 7z/7z-boundary 1.0 — 7z archives of five kinds built by Python: Copy-coded files, an LZMA file, empty streams and files with times and attributes, an empty archive, an encoded header
• ar/ar 1.0 — Unix ar archives in the System V, BSD, GNU and Microsoft COFF variants, with symbol tables, long names, thin and nested archives
• ar/ar-boundary 1.0 — Unix ar archives with header fields at their edges (symbol and name table names, references, blank and widest numbers) and short data
• arj/arj 1.0 — ARJ archives of a main header and one stored file, with header sizes and CRC-32s and extended headers
• arj/arj-boundary 1.0 — ARJ archives of one file with header fields at their edges (all host systems, garbled, secured and volume flags, every method and file type)
• cab/cab 1.0 — Cabinet files of one stored file in one data block, plain or with a reserved header area, with offsets, sizes and the CFDATA checksum (no compression, no sets)
• cab/cab-boundary 1.0 — Cabinet files with fields at their edges: reserved areas with LZX, cabinet sets with continued files, two folders stored and MSZIP, extreme dates and attributes
• cab/cab-layouts 1.0 — Cabinet files in eight layouts with every size written out: empty, reserved areas, sets, two folders, MSZIP, every compression type, deep paths
• cpio/cpio 1.0 — cpio archives in odc, newc, crc and old binary format, with name and file sizes, padding and the crc checksum
• cpio/cpio-blocks 1.0 — cpio archives of one to three one-byte files in the four formats (old binary in both byte orders), filled with zeros to a 512-byte block
• cpio/cpio-boundary 1.0 — cpio archives in the four formats with field values at their edges (every file type and special mode bit, extreme link counts and times)
• rar/rar 1.0 — RAR 4 archives of one stored file, with optional service blocks, every header's size and CRC (no compression, volumes or encryption)
• rar/rar-boundary 1.0 — RAR 4 archives with the flags and values at their edges (volumes, solid, locked, passwords, Unicode names), service, old comment and old sub blocks
• tar/tar 1.0 — POSIX ustar archives of regular and contiguous files, directories, links, devices and FIFOs, with sizes and header checksums (no pax or GNU extensions)
• tar/tar-boundary 1.0 — tar archives with fields at and past the edges (special mode bits, largest ids, V7 and old GNU magic, every POSIX, GNU and vendor typeflag, misaligned pax records)
• zip/zip 1.0 — ZIP archives of a stored file, a deflated file written as a stream with a data descriptor, and a directory, with comments (no ZIP64 or encryption)
• zip/zip-boundary 1.0 — ZIP archives of three stored entries with fields at their edges (MS-DOS and UTF-8 names, the first and last DOS dates, a 2038 timestamp, uid 0xffffffff); only the third entry's data varies

Fanbase v2026.10.20

Changes since https://github.com/fandango-fuzzer/fanbase/tree/v2026.10.15

Added

• aac/aac 1.0 — ADTS frames with a free header and a random raw_data_block, frame_length written for each payload size; files do not decode
• aac/aac-boundary 1.0 — Same as aac, with values taken from the edges of what the format allows (all profiles, sampling indices and channel configurations, CRC-protected frames), and ADIF files
• aac/aac-elements 1.0 — Complete ADTS frames, one for each syntactic element (SCE, CPE, CCE, LFE, DSE, PCE, FIL with SBR and DRC, TNS, short windows, gain control)
• flac/flac 1.0 — FLAC with one metadata block of each type and one to three CONSTANT-subframe frames; lengths and CRCs are constraints
• flac/flac-boundary 1.0 — Same as flac, with values taken from the edges of what the format allows (block sizes 16 and 65535, unknown sizes, placeholder seek points, CD cue sheet)
• flac/flac-metadata 1.0 — Metadata chains of up to six blocks in any order, then at most one complete frame of a chosen subframe kind (CONSTANT, VERBATIM, FIXED, LPC, stereo decorrelation)
• mp3/mp3 1.0 — ID3v2.3 tag, one MPEG audio frame of each kind (MPEG-1, 2 and 2.5, Layers I to III, a CRC-protected frame) with zero bodies, and an ID3v1 tag
• mp3/mp3-boundary 1.0 — Same as mp3, with values taken from the edges of what the format allows (ID3v2.3 and 2.4 flags, lowest and highest bitrates, reserved emphasis, CRC-16)
• mp3/mp3-id3 1.0 — ID3v2.2 to 2.4 tags (extended header, unsynchronisation, footer, CHAP, APIC, PRIV), one to three MPEG frames of mixed versions and layers, ID3v1, TAG+ or APEv2 trailers
• ogg/ogg 1.0 — Ogg Vorbis with the identification, comment and setup headers, sequence numbers and CRC-32 as constraints; the setup header is random, so files do not decode
• ogg/ogg-boundary 1.0 — Same as ogg, with values taken from the edges of what the format allows, plus streams of bare pages and a packet that never ends; files do not decode
• ogg/ogg-codecs 1.0 — Ogg streams of Vorbis, Opus, Theora, Speex or FLAC, with pages made by helpers that keep lacing values, sequence numbers and CRC-32 right
• wav/wav 1.0 — WAVE with a PCM or float fmt chunk and fact, data, cue, smpl, LIST/INFO, bext and JUNK chunks, sizes and counts tied together with constraints
• wav/wav-boundary 1.0 — Same as wav, with values taken from the edges of what the format allows (1 Hz to 192 kHz, A-law, mu-law, 18 channels, undefined loop types)
• wav/wav-layouts 1.0 — Eight complete WAVE layouts with every size written out (empty data, 32639 channels, metadata chunks, Broadcast Wave, nested LIST, wavl with slnt)

Changed

• png/png-container 1.0 → 1.1 — PNG chunk structure only; image data is arbitrary bytes, so most files do not decode

Fanbase v2026.10.15

Changes since https://github.com/fandango-fuzzer/fanbase/tree/v2026.10.13

Changed

• ppm/ppm 1.0 → 1.1 — P3 (ASCII) and P6 (raw) PPMs with 8-bit and 16-bit samples, header comments and whitespace
• xbm/xbm-lexical 1.0 → 1.1 — Same dialects as xbm, with the surrounding C lexical detail varied instead of the geometry (a few identifier stems, inline comments, variable-width hex literals, optional trailing comma), for sizes of 8 to 32 pixels

Fanbase v2026.10.13

Changes since https://github.com/fandango-fuzzer/fanbase/tree/v2026.10.09.1

Added

• heic/heic 1.0 — A single HEVC-coded still image in the real ISOBMFF/HEIF box layout (ftyp, meta/hdlr/pitm/iloc/iinf/infe, iprp/ipco/ispe/hvcC/pixi/colr, idat); the HEVC NAL payloads are container-correct shells, not a decodable bitstream
• heic/heic-boundary 1.0 — Same as heic, with values taken from the edges of what the format allows (degenerate/overflow spatial extents, extreme HEVC profile/level bytes, a hidden-item flag, ICC-embedded colr, and the irot/imir/pasp/clap transformative properties)
• heic/heic-box-sizes 1.0 — Six concrete file layouts (plain, extended item, transform, legacy, sequence, size-extreme) exercising ISOBMFF's zero-size ("extends to EOF") and largesize box-size conventions alongside boundary offset/length values
• heic/heic-sequence 1.0 — Same as heic, plus item references/entity grouping/protection boxes and the full timed-image-sequence (moov/trak/mdia/minf/stbl) layout used for HEIC bursts and live photos, not just a single still
• jxl/jxl 1.0 — Raw JPEG XL codestreams with a real bit-packed header and metadata; the entropy-coded frame body is a structurally-framed stub, so files do not decode
• jxl/jxl-frames 1.0 — Spells out frame internals that jxl stubs out (TOC, LFGlobal, VarDCT/Modular groups, entropy streams); uses placeholder ASCII tag bytes instead of real bit-packed encoding, so files do not decode yet
• jxl/jxl-frames-boundary 1.0 — Same as jxl-frames, with values taken from the edges of what the format allows (multiple frame types, colour spaces and extension bundles); fields use fixed byte-aligned approximations rather than true bit-level packing, so files do not decode
• ppm/ppm 1.0 — P3 (ASCII) and P6 (raw) PPMs with 8-bit and 16-bit samples, header comments and whitespace
• ppm/ppm-boundary 1.0 — Same as ppm, with values taken from the edges of what the format allows (maxval 1, 255, 256 and 65535; leading-zero dimensions; every whitespace flavour)
• ppm/ppm-stream 1.0 — A PPM image followed by zero or more further images concatenated in the same file, covering maxval's full normative range
• ppm/ppm-stream-boundary 1.0 — Same as ppm-stream, with concatenated P3/P6 images and sample bytes taken from the edges of what the format allows
• svg/svg 1.0 — Core SVG 1.1 elements (shapes, paths, text, gradients, filters, clipping/masking, markers, style/script, animation)
• svg/svg-boundary 1.0 — Same as svg, with values taken from the edges of what the format allows (huge/negative coordinates, deprecated DOCTYPEs and attributes, every legacy colour syntax, foreignObject, SMIL timing edge cases)
• svg/svg-doctype 1.0 — Same as svg, with every element's optional presentation attributes toggled individually and a choice of legacy DOCTYPE/DTD declarations (or none)
• svg/svg-extensions 1.0 — Same as svg, plus legacy SVG 1.1 font/glyph elements, draft SVG 2 paint servers (meshGradient, hatch, solidColor) and a few non-SVG embedded tags (audio/video/canvas/iframe) that real renderers treat as inert unknown elements
• svg/svg-kitchen-sink 1.0 — A single, almost entirely fixed document that packs nearly every SVG feature into one file; useful as one maximally-featured compatibility sample, not as a randomized fuzzer (little varies between runs)
• svg/svg-nested-animation 1.0 — Same as svg, grounded directly in the SVG 2 recommendation, with SMIL elements nested as children of the shape they animate instead of appearing as unrelated top-level siblings
• svg/svg-rare-features 1.0 — Same as svg, biased toward obscure and rarely-implemented corners of the spec (mesh gradients, uncommon filter primitives, baseProfile/contentScriptType and other seldom-used root attributes)
• xbm/xbm 1.0 — X11 (unsigned char/char) and X10 (short) XBM dialects, with and without a cursor hotspot
• xbm/xbm-boundary 1.0 — Same as xbm, with values taken from the edges of what the format allows (dimensions that stress ceil() row padding, a degenerate 0x0 bitmap, and hotspot values parsers rarely range-check)
• xbm/xbm-guards 1.0 — Same dialects as xbm, wrapped in #ifndef include guards or nested #if preprocessor conditionals, with both hotspot-define orderings and large/asymmetric geometries
• xbm/xbm-lexical 1.0 — Same dialects as xbm, with the surrounding C lexical detail varied instead of the geometry (arbitrary identifier stems, inline comments, variable-width hex literals, optional trailing comma)
• xpm/xpm 1.0 — Core XPM3 features one at a time (hex colours, multi-char pixels, cursor hotspot, multi-visual colour keys, XPMEXT, named colours, transparency)
• xpm/xpm-catalog 1.0 — A curated, mostly-fixed catalogue of representative example files spanning the XPM3, XPM2 and XPM1 dialects; useful as compatibility samples, with far less per-run variation than xpm or xpm-legacy
• xpm/xpm-legacy 1.0 — Same as xpm, plus the deprecated XPM1 (#define + _colors[]/ _pixels[] arrays) and XPM2 (plain-text "! XPM2") dialects, with boundary hex-width colour values and large hotspot coordinates
• xpm/xpm-lexical 1.0 — Same as xpm, with the surrounding C lexical detail varied instead (storage-class spelling, optional const qualifier, arbitrary identifiers, interspersed comments) and the fuller X colour notation catalogue (rgb:/rgbi) intensities alongside hex and named colours)

Fanbase v2026.10.09.1

A release made on request. The registry has not changed since v2026.10.09.

Fanbase v2026.10.09

The first release of the registry.