2 of 2 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; 1 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 1 failure of our instrument; 0 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/2302.09457.json · badge: /api/ran/2302.09457.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 |
|---|---|---|
| copy not recorded | community not in the paper's declared repositories |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| add_common_attack_args | Ran ran; our contract draft was wrong, not the code |
this paper's copy was not recorded; identical code first harvested from retsuh-bqw/fmp pointer only; the stored copy get_code serves, from retsuh-bqw/fmp, is pointer only (licence: NOASSERTION) · get_code("efd3b8b851a0f5e7") How it ranThe body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| compute_loss_value | Ran ran, honoured the contract we drafted |
this paper's copy was not recorded; identical code first harvested from SCLBD/BackdoorBench pointer only; the stored copy get_code serves, from SCLBD/BackdoorBench, is pointer only (licence: NOASSERTION) · get_code("855d4d7e071246f8") How it ranThe body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 2 are also present in other papers whose code we hold (2 with at least one paper dated earlier, 0 the same month, 2 later) and 0 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.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| add_common_attack_args | 8 other papers 3 dated earlier, 5 later |
1708.06733 (2017-08) BadNets: Identifying Vulnerabilities in the Machine Learning Model Supply Chain |
1905.13409 (2019-05) Bypassing Backdoor Detection Algorithms in Deep Learning 2206.12654 (2022-06) BackdoorBench: A Comprehensive Benchmark of Backdoor Learning and 5 more not named here |
| compute_loss_value | 2 other papers 1 dated earlier, 1 later |
2206.12654 (2022-06) BackdoorBench: A Comprehensive Benchmark of Backdoor Learning |
2407.19845 (2024-07) BackdoorBench: A Comprehensive Benchmark and Analysis of Backdoor Learning |
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.
Adversarial machine learning (AML) studies the adversarial phenomenon of machine learning, which may make inconsistent or unexpected predictions with humans. Some paradigms have been recently developed to explore this adversarial phenomenon occurring at different stages of a machine learning system, such as backdoor attack occurring at the pre-training, in-training and inference stage; weight attack occurring at the post-training, deployment and inference stage; adversarial attack occurring at the inference stage. However, although these adversarial paradigms share a common goal, their developments are almost independent, and there is still no big picture of AML. In this work, we aim to provide a unified perspective to the AML community to systematically review the overall progress of this field. We firstly provide a general definition about AML, and then propose a unified mathematical framework to covering existing attack paradigms. According to the proposed unified framework, we build a full taxonomy to systematically categorize and review existing representative methods for each paradigm. Besides, using this unified framework, it is easy to figure out the connections and differences among different attack paradigms, which may inspire future researchers to develop more advanced attack paradigms. Finally, to facilitate the viewing of the built taxonomy and the related literature in adversarial machine learning, we further provide a website, \ie, \url{http://adversarial-ml.com}, where the taxonomies and literature will be continuously updated.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2302.09457")
get_code_for_paper("2302.09457")
have("2302.09457")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2302.09457.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2302.09457)
Connect an agent — have() is free.