Socair reference feed

An organization’s own signed reference data for the checks to compare against: known-bad artifact hashes, reviewed chat templates, and canonical tokenizers, as a directory an air-gapped site can import.

Shape

Envelope: An in-toto Statement v1 (https://in-toto.io/Statement/v1) in a DSSE envelope with payload type application/vnd.in-toto+json, signed with Ed25519. It verifies offline: no transparency log or certificate authority is involved.
Subject: One subject per data file in the feed directory, by name and SHA-256. The statement is feed.dsse.json in that directory.

Predicate

issuer: Who issued the feed.
version: The feed’s version.
issued: When it was issued (RFC 3339).
expires: When it expires. An expired feed stops the scan.
description: Optional.

Sign and verify

socair feed sign <dir> --key feed.key --issuer <name> \
  --version <v> --expires <RFC 3339 time>
socair feed verify <dir> --keys feed.pub

What the signature means

A scan uses a feed only if it verifies: the signature against the configured feed keys, every data file against the hash the statement names, and the time window. Anything else stops the scan, because a feed changes verdicts.
Data files, all optional: denylist.txt (known-bad hashes), templates.txt and templates/<sha256>.jinja (reviewed chat templates), tokenizers.txt and tokenizers/<name>.json (canonical tokenizers).
The format is open and the issuer is whoever signs: an organization builds and signs its own feed, and a report names the feed it used. The Socair project publishes none.

Where it is defined

The feed format

The other signed documents: Socair attestation, Socair acceptance, Socair inventory snapshot, Socair OCI binding, Socair derivation record.