Open source, MIT license
Help make Evinlo better
Every part of Evinlo is open to improvement: the algorithms behind each score, the words in six languages, the code and the documents. You don’t need to write code to help.
Everything happens in the open, in the GitHub repository. Evinlo is a small volunteer project, so a little patience with replies is appreciated.
-
Algorithms
Read how a score is calculated and challenge it. Does it reflect what really happened? Where could it mislead someone? Propose a change with the algorithm proposal form, and test it with the evaluation tool: on your own Mac, it replays every area day by day on a synthetic person or on your own Apple Health export. Of your own data, share only whether the guardrails held, never the data or results from it.
-
Translations
Evinlo speaks English, German, French, Spanish, Brazilian Portuguese and Hindi. Read the app or the feedback pages in your language and tell us where a sentence sounds translated rather than written. Each language has a glossary, so that the same thing always has the same name.
-
Bug reports
Something looks wrong, or doesn’t work? Tell us what you did, what you expected and what happened instead. Please remove personal health data from screenshots and logs. A security vulnerability never goes into a public issue: follow the security policy instead.
-
Code
The app is Swift and SwiftUI without third-party dependencies, and every algorithm is plain Swift in the EvinloKit package, tested on synthetic data. Small fixes can go straight to a pull request; for anything bigger, open an issue first, so that the direction is agreed before you put in the time.
-
Documentation
Unclear wording, gaps and typos are worth a pull request on their own. Everything in the repository is written in English, in plain words, and describes what exists.
-
Feedback
Not on GitHub? Send your thoughts through the feedback form, in any of the six languages. Contributors read the public feedback too, so an idea shared there can become someone’s next pull request.
From fork to pull request
- Read the ground rules. They protect what Evinlo is: no servers and no tracking in the app, health data that stays on the device, no medical claims and no other products by name. A pull request that breaks one is not merged.
- Open an issue for anything bigger than a small fix, and use the algorithm proposal form for a change to how something is calculated.
- Fork the repository and create a branch from
main, named likefix/stage-timeline-layoutordocs/privacy-typos. - Make one focused change, with tests on synthetic data. A change to an algorithm also updates docs/scoring.md, its fixtures and its version.
- Run the tests of what you touched. CONTRIBUTING.md lists the commands.
- Commit with Conventional Commits, for example
fix(health): de-duplicate samples recorded by two sources. - Open a pull request against
main, fill in the template and link the issue. The maintainer reviews every pull request.
Where to find things
- The repository on GitHub — the app, the algorithms, the website and the documents
- CONTRIBUTING.md — the full guide: ground rules, setup, tests, pull requests
- Issue templates — bug report, feature request, algorithm proposal
- Code of Conduct — how we treat each other
- SECURITY.md — how to report a vulnerability privately
- docs/scoring.md, “Changing an algorithm” — how a change to a score is proposed, tested and versioned
- The Evinlo Explainers — each area of the app, explained in a few minutes
By contributing, you agree that your contribution is licensed under the MIT License, like the rest of Evinlo.