Home · Extensions · .parsed

`.parsed`

0 claimants 0 primary 0 secondary

SWH popularity

From 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.

56.8K

total occurrences

17.0K

since 2019 (30.0%)

2004–2023

years active

Case variants in archive: .parsed (56.7K), .Parsed (79), .PARSED (1) — aggregated above.

🪶 Orphan extension — no evidence anywhere

Total mystery. .parsed has no PL claim, no Wikidata or Wikipedia entry, no Linguist heuristic, no manual label, and no archived SWH sample. The auto-suggested label (unknown) is the rule-based guess; treat it as a starting point, not an answer. If you know what this extension is — even "it's a one-off from project X" — please submit a label below. Orphans are the highest-priority cases. Vocabulary reference: docs/extension_labels.md.

Label * If label has <...>, fill it here (e.g. for pl/<id> type rust). For multi-PL submissions, enter several pl/<id> separated by commas. Friendly name (optional) Reference URL (optional, but recommended — spec / Wikipedia / vendor) Evidence / notes *

— or, if the button is blocked, use the link just below:

(fill the form to enable this link)

What happens after I submit?

A new GitHub issue is opened in this repo with your form contents in a structured YAML block and the label ext-review. Your GitHub login becomes the annotator; the issue's created_at is the submission timestamp.
A curator script (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.
Your submission shows up on the curator triage page (/review/curator/) under "new". Maintainers review the issue (comment, ask for clarification, accept or reject) and edit extension_labels.csv to set curator_status to accepted.
For 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.
Friendly-name + reference-URL labels (e.g. 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.

SWH-mined examples (0)

No claimants, heuristics, or SWH samples indexed for .parsed yet.