SOURCE//PUBLIC · Volume 1 · Editorial field guide
A repository worth finding
A practical, testable improvement framework for research software infrastructure.
Research University editorial desk · October 29, 2026. Prepared with ChatGPT; Chief Editor: Dr. Freedom Cheteni. Editorial resource; independent human peer review is not recorded. No new funding, experimental results or DOI are claimed.
Evaluate with evidence
For each repository, test discoverability, funding provenance, version identity, licensing clarity, installation reproducibility, preservation, accessibility and maintenance transparency. Use documented observations and dates. An untested criterion is not a failed criterion.
Avoid a misleading league table
Report pass, partial, fail, not tested and not applicable for each criterion, with a reproducible test and a limitation. Do not assign numerical rankings until a published sampling and weighting protocol has been applied consistently. Invite maintainers to correct factual errors.
Make recommendations actionable
Each proposed change should identify the user problem, supporting observation, suggested implementation, likely effort and success measure. The companion series starts with proposals, not completed audits; verified evaluations can be submitted through the journal’s existing review workflow.
Primary discovery sources
These links support discovery and the described institutional scope. They do not establish funding or reproducibility for individual software packages.
- Federal repository directory ↗ — Directory
- Code.gov ↗ — Catalog
- Data.gov ↗ — Catalog
- USAspending ↗ — Funding
- Bioconductor ↗ — Package registry
- SciCrunch ↗ — Registry
- Dockstore ↗ — Workflow registry
- GitHub ↗ — Code host
- GitLab ↗ — Code host
- Zenodo ↗ — Archive
- Software Heritage ↗ — Archive
- bio.tools ↗ — Registry