How flyingdoog/awesome-graph-explainability-papers works
1. This repository is a static curated bibliography, not an application or library. Its “product” is a maintained index of graph neural network explainability papers, with hyperlinks out to papers, code, surveys, and documentation.
2. The primary entry point is README.md. It acts as the landing page and main catalog, starting with a title and short scope statement, then listing papers grouped by category and year.
3. The content model is taxonomy-first. The README organizes the corpus into major sections such as Surveys, Platforms, and then year-based collections from 2026 back to “2020 and before.” This is the main navigation structure a reader would use.
4. The most important architectural boundary is between the repository and external sources. Almost every item links out to external paper hosts such as arXiv, OpenReview, ACM/IEEE/Springer pages, and occasionally project code repositories or platform documentation.
5. The “Platforms” section is a second subsystem distinct from the paper index. It highlights tooling and benchmark ecosystems around GNN explainability, including PyTorch Geometric explainability docs and external libraries/benchmarks like DIG, GraphXAI, GraphFramEx, GNNExplainer/PGExplainer code, and BAGEL.
6. The year sections function as a chronological changelog of the research field. They do not contain executable logic; instead they encode curation data and provenance for papers, enabling the repo to serve as a historical map of the area.
7. There is also a topic-oriented view implied by bytopics.md. Even though only the filename is visible here, it likely serves as an alternate index that reorganizes the same bibliography by method family, task type, or explanation style rather than by publication year.
8. Because the repository is documentation-only, there are no runtime services, build pipelines, databases, or APIs. The only “data flow” is manual curation: papers are added or reclassified in Markdown, and readers follow the embedded links to external sources.
9. The repository’s content boundary is broad but focused: it covers explainability for graph neural networks and closely related graph learning topics, but excludes implementation details except where a paper or platform is explicitly referenced.
10. For diagramming purposes, the repo should be modeled as a two-view knowledge base: a chronological bibliography (README.md) plus a topic index (bytopics.md), both backed by external scholarly sources and platform docs.
Main entry points: README.md Platforms · bytopics.md By topics
Components 16
Repository views
Markdown entry points that curate and organize the bibliography.
- README · Main bibliography entry point and curated catalog for graph neural network explainability papers.
README.md - By topics · Topic-oriented bibliography view that reorganizes the same corpus by method or explanation family.
bytopics.md - Surveys · Curated survey papers that summarize the field and define its subareas.
README.md - Platforms · Explainability tooling, benchmarks, and ecosystem references around GNN explainability.
README.md - Year index · Year-based paper collections from 2026 back to 2020 and before, serving as the field timeline.
README.md - Paper links · Individual paper entries pointing to external publication pages and associated project pages.
README.md
External sources
Out-of-repo paper hosts, code repositories, and platform documentation linked from the bibliography.
- arXiv · Primary preprint host linked by many bibliography entries.
- OpenReview · Peer-review and discussion pages for some papers.
- Publishers · ACM, IEEE, Springer, and similar publisher pages linked from entries.
- Code repos · External implementation repositories referenced by selected papers or platforms.
- Platform docs · External documentation for explainability frameworks and benchmarking platforms.
- PyG explain · PyTorch Geometric explainability documentation referenced from the platforms section.
- DIG · External library ecosystem referenced as part of the platforms landscape.
- GraphXAI · External explainability benchmark or toolkit referenced in the platforms section.
- GraphFramEx · External benchmark ecosystem for evaluating graph explanations.
- BAGEL · Another referenced explainability platform or benchmark ecosystem.
Connections 18
- README → Surveys: organizes · README begins with a survey-oriented section.
- README → Platforms: includes · README contains a dedicated platforms and tooling section.
- README → Year index: orders by year · README presents the main bibliography as a chronological index.
- README → Paper links: lists · README enumerates individual paper entries as curated references.
- By topics → Paper links: reindexes · Topic view reorganizes the same paper corpus by theme.
- Surveys → arXiv: links out · Survey entries point to external preprint pages.
- Surveys → Publishers: links out · Survey entries may point to publisher pages.
- Year index → arXiv: links out · Chronological paper entries frequently point to arXiv.
- Year index → OpenReview: links out · Some entries point to OpenReview pages.
- Year index → Publishers: links out · Some entries point to ACM, IEEE, or Springer pages.
- Paper links → Code repos: references · Selected paper entries include project or implementation repositories.
- Platforms → Platform docs: points to · The platforms section highlights external documentation ecosystems.
- Platforms → PyG explain: includes · PyTorch Geometric explainability docs are part of the platforms boundary.
- Platforms → DIG: includes · DIG is cited as a related tooling ecosystem.
- Platforms → GraphXAI: includes · GraphXAI is cited as a benchmark or toolkit reference.
- Platforms → GraphFramEx: includes · GraphFramEx is cited as a benchmark or evaluation ecosystem.
- Platforms → BAGEL: includes · BAGEL is cited as part of the broader tooling landscape.
- Paper links → Code repos: occasionally links · Some paper entries point directly to code repositories.