Skip to main content

Manifest Check

Check an export before you rely on it

Project owners and editors can export from the Signal & Line workspace with an integrity manifest. The recipient gets the files and a manifest of their SHA-256 hashes. Load both here to see whether anything changed on the way.

Your files never leave your browser. Nothing is uploaded or stored.

Your files never leave your browser. Nothing is uploaded or stored.

This is an example, not your files. It is a made-up export in which one file was changed after it left the workspace.

Paste the public key the service publishes, in hex. It shows whether the service signed this manifest. If the key has changed since, use the one in use when the export was made.

A key inside the manifest only proves the manifest agrees with itself. To know it came from the service, check it against the public key the service publishes.

Check result

Example

One red lamp

Signal: Danger

Something doesn't match. Don't rely on this export until you know why.

Manifest digest
Matches
Signature
Valid with the embedded key
Files matched
1 of 3
Changed or unknown
1
Unverifiable
1
Not supplied
2
Project
Example: Harbour Street lease · EX-0001
Exported
2026-10-02 14:30 UTC · 4 documents, 5 versions

Manifest digest: Matches

The manifest matches its own digest, so nothing in it changed by accident. Someone editing it on purpose could work out a new digest, which is what the signature is for.

Worked out here
0114d5789644ec9579293649b2027e0435b65f5beaea7e580a3628d490571abf

Signature: Valid with the embedded key

This proves the manifest agrees with itself. It doesn't prove who made it: anyone can sign with a key of their own. Paste the published key to check that.

Key ID
147d7831f57aa6a1
Key in the manifest
6beeaaa7d687abf12690096c16923d6e7cfb5c3703967c21a26ecbd702eeca6b

File by file

  • lease.docx

    Matched

    Its hash matches the manifest, so these are the bytes that were exported.

    In the manifest
    lease.docx · Version 2Document 1, current version
    SHA-256
    2451f7b54f4fe1a53167d85b254378c2af671bcffb6cf8bc178e642e2ee63269
  • side-letter.pdf

    Unverifiable

    This version was written before the workspace hashed files, so there is nothing to compare it with.

    In the manifest
    side-letter.pdf · Version 1Document 2, current version
    SHA-256
    b6961a9a010dfcbb96625c75d07455f8397847c62d0a16ecd341575ee80c6c8e
  • rent-schedule.xlsx

    Changed

    A file with this name is in the manifest, but the contents differ. It changed after export.

    In the manifest
    rent-schedule.xlsx · Version 1Document 3, current version
    SHA-256
    98eab5e3708aaa5c506e0e084afc99171049cd439634c87c6eefff26c4619300Manifest: b3a503c4349156a320d38636dd18572c47e80be7cfcc344ecb18cd4b2d6b0324
  • No file supplied

    Not supplied

    You didn't supply this file, so it wasn't checked.

    In the manifest
    lease.docx · Version 1Document 1, earlier version
    SHA-256
    a08ba8b7e6c1d17418f00e9bf31ce55fd97164ea4538147a455e2e9a0f3b07ee
  • No file supplied

    Not supplied

    You didn't supply this file, so it wasn't checked.

    In the manifest
    draft-notice.docx · Version 1Document 4, deleted version
    SHA-256
    8adbedf59b0ab7525dc87d7bf82f5eb650297c45b5bd5068965b387d98db59f9

Reading the result

What each check proves

Each check answers one question. None of them says whether a document is right, only whether it is the one that was exported.

  • Manifest digest

    Proves

    The manifest is the one the workspace sealed. Nothing in it changed by accident or through a careless edit.

    Doesn't prove

    On its own it can't stop a deliberate edit. Whoever edits the manifest can work out a new digest to match.

  • Signature, embedded key

    Proves

    The digest was signed and hasn't changed since. The manifest agrees with itself.

    Doesn't prove

    It doesn't show who signed it. Anyone can swap in a key of their own and sign again.

  • Signature, published key

    Proves

    The holder of the key you pasted signed this manifest. If that is the workspace's published key, the export came from the workspace.

    Doesn't prove

    It is only as good as the key you paste. Get it from the service itself, not from whoever sent you the files. If the key has changed since, use the one in use when the export was made.

  • File hashes

    Proves

    A matched file has exactly the bytes the workspace recorded for that version, down to the last bit.

    Doesn't prove

    It says nothing about whether the document is right, or about files you didn't supply. A version written before the workspace hashed files can't be checked at all, so it shows as unverifiable.

The check reads the manifest format the workspace uses today. It runs in your browser with the standard Web Crypto tools, and you can repeat any part of it with a command such as shasum -a 256. It doesn't replace your own judgement about the documents.

Trust you can check

Read how the Signal & Line workspace keeps its records, or try the other tools.