Support

One inbox, read by the people who built it: [email protected]. We aim to reply within one business day.

Go straight to the right place

• Billing, invoices, cancelling, payment method — your account handles all of it, immediately.
• Refunds — how refunds work, or just email us.
• A score looks wrong — see corrections and disputes below. Include the capability page and what the evidence should say.
• How the score is computed — the methodology shows the whole formula, including what we deliberately don't measure.

Licence keys

Your key is in your account. Switch it on once per machine:

Same command as the free one; the rows with an answer now show it. If you would rather query the history yourself, the key is also a bearer token:

A 403 means the key isn't valid or the subscription lapsed; a 503 means validation is temporarily unavailable — retry rather than re-issuing your key.

Treat the key like a password: anyone holding it can use your subscription. If it leaks, revoke it in your account and a new one is issued.

Corrections and disputes

Every number here is derived from public evidence, which means every number can be wrong in a way you can point at.

If a score, a grade, a security finding or a label is wrong about your capability — or about one you rely on — say so and we will fix the data or explain why it stands.

Email [email protected] with CORRECTION in the subject, or use the something wrong here? link at the foot of any capability page — it carries the capability's id for you.

Tell us what the page says, what you believe is true, and where that can be checked publicly.

• What we correct. Wrong identity or ownership, a repository or package we linked to the wrong thing, a stale advisory, a mis-detected install script or permission, a duplicated or mislabelled listing, or a measurement contradicted by its own public source.
• What we will not change. A rank or a score that the evidence supports. Nobody can buy, request or negotiate a position — that is the whole product, and it applies to complaints as firmly as it applies to payment.
• How it resolves. We reply with what we found. A data fix lands on the next pipeline run and the page's Measured date moves with it. If we disagree, you get the reasoning and the public source we relied on, and you are free to publish both.
• Disputed while we look. If a claim is materially contested we say so on the page rather than quietly leaving it up.

Security

Found a vulnerability in tashan itself? Email [email protected] with SECURITY in the subject and we'll respond before anything else in the queue. Please don't file it publicly first.

Note that we do not audit the capabilities we measure — a tashan score is not a security review. If you find a malicious capability, report it to its registry and tell us so we can flag it in the data.