6 of 6 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; 5 failures 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/2307.15971.json · badge: /api/ran/2307.15971.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 |
|---|---|---|
| bapfl/code | canonical (classifier label) classifier basis: census |
6 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| avg_metric | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
bapfl/code/utils/set_md.py pointer only (licence: NONE) · get_code("7e608ae08522865c") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, bapfl/code when it was checked. 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. |
| clip_norm | Ran ran; our contract draft was wrong, not the code |
bapfl/code/utils/utils.py pointer only (licence: NONE) · get_code("00d8f2684c594e42") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, bapfl/code when it was checked. 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. |
| fed_average | Ran ran; our contract draft was wrong, not the code |
bapfl/code/utils/utils.py pointer only (licence: NONE) · get_code("32729b112d68b837") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, bapfl/code when it was checked. 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. |
| flatten_shared_parameters | Ran ran, honoured the contract we drafted |
bapfl/code/utils/utils.py pointer only (licence: NONE) · get_code("0d2cd350ec88e2cf") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, bapfl/code when it was checked. 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. |
| make_layers | Ran ran; our contract draft was wrong, not the code |
bapfl/code/models/Cifar10Net.py pointer only (licence: NONE) · get_code("69cb81ed8262cd92") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, bapfl/code when it was checked. 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. |
| vgg11 | Ran ran; our contract draft was wrong, not the code |
bapfl/code/models/Cifar10Net.py pointer only (licence: NONE) · get_code("9ef94bd9488b7ebe") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, bapfl/code when it was checked. 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 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 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 6 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.
Existing research primarily focuses on backdoor attacks and defenses within the generic federated learning scenario, where all clients collaborate to train a single global model. A recent study conducted by Qin et al. (2023) marks the initial exploration of backdoor attacks within the personalized federated learning (pFL) scenario, where each client constructs a personalized model based on its local data. Notably, the study demonstrates that pFL methods with \textit{parameter decoupling} can significantly enhance robustness against backdoor attacks. However, in this paper, we whistleblow that pFL methods with parameter decoupling are still vulnerable to backdoor attacks. The resistance of pFL methods with parameter decoupling is attributed to the heterogeneous classifiers between malicious clients and benign counterparts. We analyze two direct causes of the heterogeneous classifiers: (1) data heterogeneity inherently exists among clients and (2) poisoning by malicious clients further exacerbates the data heterogeneity. To address these issues, we propose a two-pronged attack method, BapFL, which comprises two simple yet effective strategies: (1) poisoning only the feature encoder while keeping the classifier fixed and (2) diversifying the classifier through noise introduction to simulate that of the benign clients. Extensive experiments on three benchmark datasets under varying conditions demonstrate the effectiveness of our proposed attack. Additionally, we evaluate the effectiveness of six widely used defense methods and find that BapFL still poses a significant threat even in the presence of the best defense, Multi-Krum. We hope to inspire further research on attack and defense strategies in pFL scenarios. The code is available at: https://github.com/BapFL/code.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2307.15971")
get_code_for_paper("2307.15971")
have("2307.15971")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2307.15971.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2307.15971)
Connect an agent — have() is free.