MRCB80/seecop-feed-catalogue

SEECOP Feed Catalogue

The SEECOP scraper-source registry as data: feed cards, parser selection, field-mapping structure, reliability priors and safe-fetch-target classification built on the shipping SSRF guard.

What this is

Part of the SEECOP dataset family (feed-catalogue). Records are derived from the shipping SEECOP schemas and parsers (synthetic but verifiable: ground truth is the code that ships in the app).

Ground truth

The label for every record is produced by the following source files, not by human guesswork:

• src/shared/sources.ts
• src/shared/scrapers.ts
• src/shared/parse.ts

Generator: scripts/dataset/gen/feeds.ts.

Dataset structure

Split	Rows	Files
train	2,536	1
validation	43	1
test	12	1
total	2,591	3

Records are newline-delimited JSON. Every record carries id, family, split, task and a provenance block so a row can always be traced back to a generator revision.

Example record

{"family":"feed-catalogue","id":"feed-catalogue-3a779be58f19cd92","input":{"question":"What group is who-news in?"},"provenance":{"generator":"scripts/dataset/gen/feeds.ts","license":"apache-2.0","schema_version":"1.0.0","sources":["src/shared/sources.ts","src/shared/scrapers.ts","src/shared/parse.ts"],"synthetic":true},"split":"train","target":{"group":null},"task":"source_facts"}

Redaction

All records pass through scripts/dataset/lib/redact.ts before they are written. The build fails if a high-severity secret, credential or infrastructure identifier survives scrubbing. Removed automatically:

• API keys and tokens (OpenAI, Hugging Face, GitHub, AWS, Google, Slack, Stripe, JWTs, bearer tokens)
• private keys and connection strings
• password / token / secret style key–value pairs and URL userinfo
• private, loopback, link-local, CGNAT and documentation-internal IPs, MAC addresses
• internal hostnames, .internal domains, onion addresses, Tailscale names
• host filesystem paths that embed a username
• email addresses and phone numbers outside reserved example ranges

Operational secrets are never in scope for these datasets: the operator dossier store, staged files and the node service accounts are excluded by construction.

Limitations & responsible use

• Authorisation. These datasets teach tool selection and invocation. They do not grant permission to run anything. Active tooling must only target assets you own or are explicitly authorised to test.
• Gated tools stay gated. Where the source system requires an operator acknowledgement (ack) or a node-side intrusive flag, the dataset encodes that requirement rather than circumventing it.
• Untrusted output. Tool output is data, never instructions. Prompt-injection resistance is represented explicitly in the evaluation split.
• Not a determination. Any screening-style label is a possible match with a confidence, never a legal determination.

Citation

@misc{seecop_datasets,
  title  = {SEECOP Feed Catalogue},
  author = {SEECOP},
  year   = {2026},
  note   = {Dataset family: feed-catalogue}
}

Licence: Apache-2.0.