7 of 11 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 7 have no contract verdict; 0 failures of our instrument; 4 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2303.14443.json · badge: /api/ran/2303.14443.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| rub-syssec/adversarial-papers | canonical (classifier label) classifier basis not recorded on the link |
7 ran · 4 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| clean_dict | Ran ran on a synthesized input |
rub-syssec/adversarial-papers/src/utils/attack_utils.py code served (permissive licence) · get_code("0937897fc19205b4") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| clean_text | Ran ran on a synthesized input |
rub-syssec/adversarial-papers/src/utils/attack_utils.py code served (permissive licence) · get_code("0f71c17baa894982") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| create_candidate_grid | Ran ran on a synthesized input |
rub-syssec/adversarial-papers/src/featurespace/grid.py code served (permissive licence) · get_code("8e279b7552181c6b") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| find_words | Ran ran on a synthesized input |
rub-syssec/adversarial-papers/src/utils/pdf_utils.py code served (permissive licence) · get_code("055f094867896073") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| get_topics_to_words | Ran ran on a synthesized input |
rub-syssec/adversarial-papers/src/utils/lda.py code served (permissive licence) · get_code("4e6dbc7d248497e2") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned dict. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| is_digit | Ran ran on a synthesized input |
rub-syssec/adversarial-papers/src/utils/pdf_utils.py code served (permissive licence) · get_code("a6a3554de7bb5b0f") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned bool, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| scrape_via_pdftotext | Ran ran on a synthesized input |
rub-syssec/adversarial-papers/src/utils/pdf_utils.py code served (permissive licence) · get_code("9ab978c5f5b548e3") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| append_to_dataframe | Not yet run unverified (harvested, no recorded run) |
rub-syssec/adversarial-papers/src/hypersearch.py code served (permissive licence) · get_code("2c8daba027e681a1") How it ranno invocation recorded. |
| get_lda_topics | Not yet run unverified (harvested, no recorded run) |
rub-syssec/adversarial-papers/src/utils/lda.py code served (permissive licence) · get_code("a7ed4609df93b63f") How it ranno invocation recorded. |
| loss | Not yet run unverified (harvested, no recorded run) |
rub-syssec/adversarial-papers/src/featurespace/loss.py code served (permissive licence) · get_code("dad61bce0b70cf63") How it ranno invocation recorded. |
| surrogate_loss | Not yet run unverified (harvested, no recorded run) |
rub-syssec/adversarial-papers/src/featurespace/attack.py code served (permissive licence) · get_code("0277b131c214088f") How it ranno invocation recorded. |
Of 11 samples lifted from this paper's linked repositories, 11 carry a function identity and 0 do not. Of the 11 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 11 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
The number of papers submitted to academic conferences is steadily rising in many scientific disciplines. To handle this growth, systems for automatic paper-reviewer assignments are increasingly used during the reviewing process. These systems use statistical topic models to characterize the content of submissions and automate the assignment to reviewers. In this paper, we show that this automation can be manipulated using adversarial learning. We propose an attack that adapts a given paper so that it misleads the assignment and selects its own reviewers. Our attack is based on a novel optimization strategy that alternates between the feature space and problem space to realize unobtrusive changes to the paper. To evaluate the feasibility of our attack, we simulate the paper-reviewer assignment of an actual security conference (IEEE S&P) with 165 reviewers on the program committee. Our results show that we can successfully select and remove reviewers without access to the assignment system. Moreover, we demonstrate that the manipulated papers remain plausible and are often indistinguishable from benign submissions.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2303.14443")
get_code_for_paper("2303.14443")
have("2303.14443")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2303.14443.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2303.14443)
Connect an agent — have() is free.