Prezenti backs builders on evidence of what they have actually shipped — not on where they studied, who they know, or how many stars a repository has.
Your public code activity is scored against a fixed rubric. Four signals carry most of the weight.
Stars and follower counts are not scored at any weight. They measure access, and access is exactly what this is built to look past.
The rubric is published in full, along with the code that applies it. Clone it and reproduce your own score:
git clone https://github.com/prezenti/talent-engine
cd talent-engine
python3 -m talent_engine.cli score \
--program prezenti-sponsorship-trial --handles YOUR_GITHUB_HANDLE
If a number looks wrong to you, you can show us exactly where — which is the point of publishing it. Every score comes with linked evidence for each component; a score with no evidence behind it cannot be produced.
The automated score produces a shortlist. People decide, after reading the evidence and talking to you. No one is funded or refused by a number.
The checks that flag manipulated profiles are published alongside the rubric — including an honest account of what they do not yet catch. We would rather tell you that than imply a precision the method does not have.
Public code activity only. Nothing about your background is inferred — there is nowhere in the system to record an inferred trait. Anything about your circumstances enters because you chose to tell us. Your contact details are stored separately from everything used for assessment, and never appear in an assessment record.
Canonical terms: prezenti-sponsorship-trial-2026-08-18-v4 terms-version: 601b9cc0a959.
These are enforced by the code that runs this programme: a policy that takes equity, leaves the give-back uncapped, lets it run forever, or fails to state what we owe you will not load, and the service will not start.
Applications close when the fifth place is filled, or 2026-12-29, whichever comes first.