The syntax and concrete variant confirmed from the file content, such as JSON, JSON Lines, Source Map v3, XML, YAML, INI, dotenv, GYP, an Apple property list, an ordered rule file, or a SHA-256 manifest.

The root structure produced by the parser, such as object, array, scalar, XML element tree, sectioned configuration, assignment set, record stream, ordered pattern list, checksum manifest, or empty marker.

The measured number of parsed structural nodes or records, including mapping and sequence nodes, XML elements, configuration entries, ordered rules, line-delimited records, or checksum entries.

The deepest parsed level in the document or record structure. Objects, arrays, XML descendants, sections, and nested build/configuration structures contribute to this measured depth.

The measured total of mapping keys, configuration names, XML attributes, manifest fields, and other named fields discovered by the parser.

The measured number of terminal values—strings, numbers, booleans, nulls, XML text values, configuration values, rule expressions, and checksum/path values—contained in the parsed artifact.

The occurrence count found through a fixed reference-field allowlist and explicit record semantics—URLs, paths, includes, source-map sources, schemas, build inputs, rule paths, and checksum targets—without guessing from arbitrary strings.

The result of the file-level extraction: Parsed, Partial, Empty, Unsupported, or Failed. Unreadable or invalid files are reported explicitly instead of receiving extension-based placeholder prose.