Make the method traceable
Cite the tool you actually used.
If Vahtian helped you search, screen, extract, test, or check citations, name the specific tool in your methods and references. That lets another researcher see what shaped the workflow and which version you ran.
Author: Heidi Helena Andersén (ORCID 0000-0001-5923-5865). The tools are archived on Zenodo, so a citation can carry a DOI rather than only a page URL.
Recommended format
Software citation — author, year, tool, version, publisher, and a persistent link:
Andersén, H. H. (2026). <Tool> (Version <x.y>) [Computer software]. Vahtian. https://vahtian.com/<tool>/
A DOI is archival and versioned, so reviewers prefer it over a plain URL. Two exist, and they point at different things:
| DOI | What it resolves to |
|---|---|
10.5281/zenodo.21700192 |
v0.2.0, released 2026-07-30. One frozen snapshot. Cite this when it matters that the code you ran can be recovered. |
10.5281/zenodo.21339127 |
All versions. Always resolves to the newest release. Cite this when you mean the project rather than one release. |
For a methods section, cite the version: the all-versions DOI moves under your reader. The difference is worked through in how to make your analysis code citable.
Per-tool citations
Replace year and version as appropriate. The page URLs are stable. There is no separate DOI per tool: the tools are archived together, so add the version DOI above when you want a permanent identifier, and keep the tool named so a reader knows which one you used.
| Tool | Citation |
|---|---|
| CiteVahti | Andersén, H. H. (2026). CiteVahti [Computer software]. Vahtian. https://vahtian.com/citevahti/ |
| StudyVahti | Andersén, H. H. (2026). StudyVahti [Computer software]. Vahtian. https://vahtian.com/studyvahti/ |
| MethodVahti | Andersén, H. H. (2026). MethodVahti [Computer software]. Vahtian. https://vahtian.com/methodvahti/ |
| DictVahti | Andersén, H. H. (2026). DictVahti [Computer software]. Vahtian. https://vahtian.com/dictvahti/ |
| MatchVahti-Lite | Andersén, H. H. (2026). MatchVahti-Lite [Computer software]. Vahtian. https://vahtian.com/matchvahti-lite/ |
| ReviewVahti | Andersén, H. H. (2026). ReviewVahti [Computer software]. Vahtian. https://vahtian.com/reviewvahti/ |
| ExtractVahti | Andersén, H. H. (2026). ExtractVahti [Computer software]. Vahtian. https://vahtian.com/extractvahti/ |
| GuidelineVahti | Andersén, H. H. (2026). GuidelineVahti [Computer software]. Vahtian. https://vahtian.com/guidelinevahti/ |
| SynthVahti | Andersén, H. H. (2026). SynthVahti [Computer software]. Vahtian. https://vahtian.com/synthvahti/ |
MatchVahti (the full app) is a separate product — cite it by name and the page you used; it has no public archive.
BibTeX
Template. Change title and url to the tool you used:
@software{vahtian_citevahti_2026,
author = {Andersén, Heidi Helena},
title = {CiteVahti},
year = {2026},
version = {v0.2.0},
publisher = {Vahtian},
doi = {10.5281/zenodo.21700192},
url = {https://vahtian.com/citevahti/},
note = {Computer software, ORCID 0000-0001-5923-5865}
}
Citing the project rather than a release? Drop version and use the all-versions DOI 10.5281/zenodo.21339127.
Citing Vahtian generally
The archived release, which is the one to use in a methods section:
Andersén, H. H. (2026). Vahtian: human-first, auditable research-integrity tools (Version v0.2.0) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.21700192
All versions
Andersén, H. H. (2026). Vahtian: human-first, auditable research-integrity tools [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.21339127
GitHub also offers “Cite this repository” from the CITATION.cff in the source repo, which carries the all-versions DOI.
A star on that repo is not a citation and says nothing about the work, but it does help other researchers find the tools.