MachineTradecraft
Global site search

Search guides, labs, glossary, and research

Type two or more characters to search.

Start with a channel, artifact, or defense term

Examples include zero-width, metadata, tokenizer, or prompt injection.
    Supply Chain · Stale or unverified artifact metadata

    Manifest and Provenance Inspector

    The inspector validates structure, identifiers, digests, graph references, and claim boundaries while refusing remote resolution or cryptographic trust claims.

    Browse all labs Open universal Machine View
    Quick answer

    What does the Manifest Inspector show?

    The inspector validates structure, identifiers, digests, graph references, and claim boundaries while refusing remote resolution or cryptographic trust claims.

    Human visibility
    Manifest, graph, and attestation claims
    Machine receiver
    Offline structural parser
    Robustness
    Format and policy dependent

    Research boundary: this page uses bounded, inert data and fixed safe examples. It never executes decoded content, requests secrets, calls third-party services, or performs actions against external systems.

    FIRST RUN / THREE STEPS

    Start with the prepared, bounded workflow.

    Nothing runs automatically
    1. Review the prepared starter input

      A bounded benign input is already present. Change it only when you are ready to test a different authorized artifact.

    2. Run Inspect manifest structure

      Run the normal first-pass analysis for the prepared values above.

    3. Scan before expanding

      Read the summary first, then scan findings and expand only the machine views you need.

    INPUT / CONTROL PLANE

    Prepare the input and choose one action.

    Ready

    The recommended first run is separated from alternate analyses. Inputs and selected files stay on this host.

    Current input state Prepared starter input loaded

    The form is prefilled with a bounded safe starting point. Nothing runs until you choose an action.

    484 / 48,000 bytes

    Maximum 48,000 UTF-8 bytes. External references are listed but never fetched.

    Maximum: 48,000 UTF-8 bytes.

    Switch prepared example5 options

    Loading a sample changes only the form values. Review the result and run an action yourself.

    Prepared benign examples
    ACTION HIERARCHY

    Run the recommended first pass.

    Alternate actions remain available below, but the first pass is the clearest place to start.

    Inputs remain on this host. Text operations are size-limited; uploaded files are processed from PHP’s temporary upload and are not retained by the application.

    OUTPUT / MACHINE VIEWS

    Scan the result from summary to evidence.

    Run Inspect manifest structure to create the first result.

    The prepared starter input is ready. The output will lead with a summary and visible qualifications before the expandable machine views.

    SummaryFindingsMachine views
    Interpretation framework

    The same artifact can produce several valid observations.

    01

    Human view

    What a person naturally reads, sees, or hears.

    02

    Structural view

    What a parser, DOM, container reader, or metadata extractor exposes.

    03

    Decoder view

    What becomes meaningful only with a rule, key, tokenizer, model, or tool.

    04

    Defensive view

    What normalization, rendering, OCR, canonicalization, or policy changes.

    Evidence and decision boundary

    Use the result as bounded evidence, not as a universal verdict.

    The inspector validates structure, identifiers, digests, graph references, and claim boundaries while refusing remote resolution or cryptographic trust claims.

    LOCAL MODEInert structural manifest and provenance inventory
    REVIEW DATE2026-08-26
    SOURCE BODYPreserved separately from implementation claims
    Computed locally

    Deterministic output produced by this bounded runtime.

    • Exact bounded source, JSON syntax, selected XML text patterns, component/name strings, internal references, digest syntax candidates, duplicate values, and provenance-related claims
    • A deterministic normalized summary and local JSON download
    • No package, dependency, vulnerability feed, certificate, transparency log, registry, or external reference is contacted
    Bounded approximation

    Useful subset or model that does not establish full conformance.

    • Format detection and field inventory are heuristic and do not provide full SPDX, CycloneDX, in-toto, SLSA, DSSE, or model-card schema validation
    • Digest syntax checks do not bind claims to downloaded artifacts
    • Graph completeness, license meaning, vulnerability applicability, builder identity, and policy compliance are not established
    Escalate for

    Claims that require an exact parser, trust system, model, or human review.

    • Cryptographic verification requires the exact artifact digest, envelope, certificate or identity policy, transparency evidence, and trusted verifier
    • Dependency and vulnerability status require authorized current registries and feeds
    • Build-provenance claims require expected builder identities and consumer-side policy enforcement
    Interpretation rule

    Record the receiver and transformation.

    Machine-decodable is receiver-relative. Record the parser, preprocessing, codebook, tokenizer, key, model, and transformation path before generalizing from one result.

    Limitations

    What this page does not prove

    Structural inspection does not validate signatures, transparency logs, registry state, vulnerability status, licenses, builder identity, or artifact safety.

    Deterministic review material

    Download the exact benign fixtures used for the evidence boundary.

    These local files are supplied for repeatable inspection. The application does not fetch them automatically, execute their content, or treat a fixture result as external verification.

    CycloneDX dangling-reference example

    Provides a valid-looking CycloneDX structure with one deliberately dangling local dependency reference; the lab must not resolve it over the network.

    Type
    JSON fixture
    Bytes
    583
    SHA-256
    34982ecc22be0190065e…
    Download fixture

    Download the complete evidence-review fixture pack · SHA-256 sidecar included beside the archive

    Continue the investigation

    Related labs and source reports

    Software and AI Artifact Provenance: SBOMs, SLSA, SPDX, CycloneDX, Sigstore, and ML Supply Chains Research report
    Continue exploring

    Move from the current explanation to a related guide, evidence source, or controlled workbench.

    Laboratory catalogChoose a focused local experimentBrowse 38 bounded laboratories spanning representation, files, messages, models, provenance, agents, supply chains, and defense.Open this path Field guideDefine Machine Tradecraft preciselyUse the formal model, classification test, taxonomy, and limits before generalizing from one artifact.Open this path Defensive architectureBuild a safer model-ingestion boundaryPreserve evidence, compare representations, canonicalize allowlisted fields, retain provenance, and minimize privilege.Open this path