How Recheckable scores are made

A score shows how much of a project’s control structure, code and contact information could be checked from public sources on the date shown: who can change the program (upgrade authority, multisig), whether the deployed code can be matched to public source code, whether code, documents and audits are public (audits are found automatically at the project’s own GitHub organisation and website; a missing audit is shown as “not found in what we searched” or “not read”, never as proof that none exists), and whether there is a way to reach the team.

It does not measure whether a project is safe, honest, lawful or a good investment. A high score does not mean low risk, and a low score often reflects missing or unreadable public evidence, not misconduct. Nothing on this site is financial, investment, legal or security advice.

• Automated checks of public data. Fixed, published checks read the Solana chain (RPC), the OtterSec build registry, GitHub and the project’s own website. Each check has a result, a source link and the date it was checked, and we store a hash of what we fetched so anyone can compare.
• No manual selection. We do not pick which projects get a score or what the result is. Every project in our index goes through the same engine and the same rules. A project’s score is shown only when its automatic checks have run at least twice, at least 24 hours apart, with the same result, when enough could be checked (coverage of at least 70 %), when nothing unusual was flagged (during the beta there is no extra waiting period). Unusual results (a big jump between two runs, a source that blocked us, a phrase that looks like a request for a seed phrase) are held for a person to look at.
• No payment influence. Payment, claiming a page, replying to a score and public pressure never change a score, its coverage or its place in a list. AI never affects a score; it only writes labelled summaries.
• One rule book. Weights and thresholds are our own editorial choices and are published on the Methodology page together with the version of the method that produced each score.

“Listed, not yet scored”

Some projects are listed by name, category and links before they have a published score. This only means that no automated score has been published for them yet (the automatic checks may still be running, the publication conditions may not be met yet, or too little could be checked from public sources). It is neutral: it is not a low score and says nothing about the project.

An automated score can occasionally be wrong. We would rather say so than hide it. The usual causes:

• A source could not be reached. If our checker could not read a source (timeout, a block, an empty page), the check is shown as “Not read”. That costs the project no points, it lowers coverage, and below 70 % coverage no grade is shown. It is not a finding about the project.
• Errors in our checks or data mapping, for example a wrong repository, address or domain linked to a project, or a page we misread.
• Stale data. A score is a snapshot. After 30 days, or when something we monitor changes, the badge turns grey, which means “changed or out of date”, not “bad”.
• Public data can itself be wrong or incomplete.

• Send a correction. Use the corrections form or write to info@recheckable.com and point to the evidence (an address, a transaction, or a page on the project’s official domain). We re-run the check. If the data is wrong we fix the mapping and recompute, and the fix is written in the change log. We never change a score because someone asks, only because the evidence changed.
• “Disputed”. If a request points to evidence that the data behind a check may be wrong, the check is marked “Disputed, under review since [date]” and keeps its last published state. We do not hide it. If the disputed check could change the grade by one band or more, the grade can be paused for at most 10 working days. Details.
• Claim the page. If your team controls the upgrade authority, official domain or GitHub organisation, you can claim your page (every project page has a “Claim this page” link; free, no review by us) and then add your own statements and a reply next to any check. Claiming never changes a score.
• Opt out. Listings made from public data without the project’s involvement can ask to be removed: opt-out.

Response times are targets, not guarantees. The page Corrections & right of reply shows the median time to resolve requests once enough have been handled.