.codeFrom the SWH-MSR-ARV dataset (Desmazières, Di Cosmo, Lorentz, MSR 2025; file nb_extensions_alphanum.csv) — one row per (ext, year) in the full SWH archive. Case-aggregated. citation.
Case variants in archive: .code (1.8M), .CODE (406), .Code (187), .cOdE (1), .cODE (1) — aggregated above.
No PL in our taxonomy claims this extension. If you know what it's used for, fill the form below. Vocabulary reference: docs/extension_labels.md.
ext-review.
Your GitHub login becomes the annotator; the issue's
created_at is the submission timestamp.tools/process_extension_labels.py)
fetches all ext-review issues and writes their
parsed contents into
data/derived/extension_labels.csv with
curator_status="new". Until this script runs, your
submission lives only as the GitHub issue.extension_labels.csv to set
curator_status to accepted.pl/<id> labels, build_pl_taxonomy.py
promotes accepted labels into
ext_claim.csv with
source="manual_review:<your-login>" and
strength="proposed". The next site rebuild then
shows your claim on this extension's page and on the
language's page.binary:image for .png) are not
promoted into ext_claim.csv (they aren't PL
claims) but are surfaced on this page's "Prior labels"
table so anyone landing here sees them next to the auto-detected
category.In short: submitting opens an issue (provenance), and a small ingestion pipeline turns issues into rows the site renders. The loop is currently manual (the curator script must be run by a maintainer); GitHub Actions could automate it on each new issue.