poka.sh

 Docs

Depth tiers

explanation

The README headline counts manifests. A manifest can be a full decoder or a route to a plain-text reader. The depth tiers sort every manifest into one tier so the count says something about depth. The numbers live in the generated scorecard; this page explains what the tiers mean and what they cannot prove.

The tiers

Tier What it is
T1 Parser with a shared viewer The crate decodes the format into a typed AST for a shared viewer.
T2 Standalone parser The crate writes a complete PreviewResponse itself.
T3 Metadata card The crate reads the file far enough to fill a titled list of key and value entries.
T4 Alias-only route No crate of its own: another module's wasm under a new id, name and extension.
T5 Hex stub Retired. The tier stays as a guard against hex-only shells coming back.
T6 Disabled The host skips registration.

Every manifest is in exactly one tier. The first match wins, in the order disabled, hex stub, alias-only route, standalone, metadata card, shared viewer.

What a tier does not prove

A tier comes from the manifest and the routing files. No source file is parsed for meaning, so a tier cannot see:

  • How much of the format a parser decodes. A tree of a few top-level keys and a full decoder of a binary container are both T1. That is what the breadth tiers are for.
  • Whether the output is correct.
  • Whether a route's module understands this specific format. A T4 route is only as good as the corpus sample someone ran through it.

For how much of a format is read, look for its breadth tier on the format page (not every format has been assessed yet), then the crate's module documentation and its tests/samples.rs. Test a parser says how to prove coverage.

Why not hex stubs

A hex dump says "this file exists" and nothing else. Poka removed the hex-only formats. A format Poka cannot parse is not routed at all, so a count of supported formats never includes a file that opens as bytes.

See also