How to cite EvidenceHelix
EvidenceHelix includes a root CITATION.cff file so GitHub and citation-aware research tools can expose machine-readable software citation metadata.
For reproducibility, citing “EvidenceHelix” alone is not enough. Record the exact release tag or Git commit used, plus the scientific sources, datasets, model versions, and relevant software dependencies behind the result.
Preferred software citation
EvidenceHelix contributors. (2026). EvidenceHelix [Computer software]. GitHub repository: mergemaven11/EvidenceHelix. Project site: evidencehelix.com.
If an archived release later receives a DOI, the DOI should become the preferred immutable citation while the exact release/commit remains in the computational record.
Minimum reproducibility record
| Layer | Record | Why it matters |
|---|---|---|
| EvidenceHelix | release tag + Git commit SHA | Pins the application and research logic used. |
| Scientific source | DOI, PMID/PMCID, registry ID, dataset accession, or canonical URL | Pins the evidence behind the claim. |
| Dataset | provider revision, retrieval date, license, file hash | Datasets evolve and may be corrected. |
| Algorithm | method name, implementation version, parameters | Prevents an analysis label from hiding different computations. |
| Software | Python/Java/package versions and container image digest when relevant | Computational environments can change outputs. |
| Model | model identifier, version/hash, prompt or configuration where material | AI behavior is version dependent. |
| Output | artifact hash + timestamp + parent provenance | Links conclusions to immutable derived artifacts. |
Why CITATION.cff exists
Citation File Format is a machine-readable way for software projects to describe how they should be cited. EvidenceHelix uses it for the platform itself; scientific conclusions still require citations to the underlying scientific evidence.
See also Sources, data & software methods.