Skip to content
MLReps

Terms

Your code stays yours, and we do not touch it.

These are the terms of using MLReps. They are written to be read rather than to be impenetrable, and where something is a property of how the software is built, they say so.

MLReps is a digital product. A data request, a deletion request or a security report reaches us at connect@mlreps.com — the same address published in our security.txt.

What it costs

Running the scan on your own machine and reading its summary in your terminal costs nothing. Publishing a full audit to your dashboard costs $1, drawn from a balance you top up in advance; there is no subscription and nothing is charged per developer. Pricing lists the price, what an audit is, and the things that are never charged — among them code that has not changed since the last audit. If what things cost ever changes, it changes with notice and never retroactively, and never for a balance you have already bought.

Early access, and what a pre-order means

Your balance becomes usable when paid scanning goes live. Until then this is a pre-order: you are buying audits at the early-access rate, not audits you can run today. So an early-access purchase buys a balance of audits at the early-access rate, and that balance becomes spendable when paid scanning is live. It does not expire.

You can ask for a full refund of anything unused within 7 days of paying — counted from the day you pay, not from the day scanning goes live. If we never ship paid scanning, you are entitled to the whole of what you paid back, and the 7-day window does not limit that — a refund window is for people who changed their mind, not a deadline for us to deliver against.

Payment is taken by a payment provider on its own page — we never receive your card details, and nothing of ours ever contacts them. Your balance appears once we credit the payment against the reference the provider gave it, which today we do by hand. If it has not appeared, send us that reference and we will credit it; the reference is also what makes it impossible for one payment to be credited twice.

Where this applies

MLReps is open to anyone, anywhere in the world. There is no country restriction, no waiting list and no approval step. We do not ask where you are, we do not block anywhere, and nothing we store holds a territory — so this is not a policy that could quietly change without the code changing with it.

Your code stays yours

You keep every right to your code. Nothing you connect grants us a licence to it beyond reading it in order to produce your own analysis for you, and we do not use your code to train anything. Your source is never stored — that is a property of the schema, not a policy, and Privacy says how.

The only thing we write is a pull request you review

One instrumentation file, on a branch of its own, opened only when you ask for it in MLReps. No push to your default branch, no merge, no second file. A fix is never committed — it stays a patch you apply yourself. Our pull-request check reports neutral and can only report neutral, so it is structurally incapable of blocking your merge. These are the commitments here that are enforced by how the software is built rather than by this page: the commit token names one repository and is revoked before the call returns.

What the findings are, and what they are not

Findings are information about your codebase, produced by rules over what the scan could read. They are not professional, legal or security advice, and they are not a warranty about your software. Where the analysis could not read part of your repository it tells you so on the screen — a region it could not read is never presented as one it read — and decisions you make from a finding remain yours.

Using it reasonably

Connect repositories you are entitled to connect. Do not use MLReps to analyse code you have no right to, to attack the service or anybody else through it, or to try to reach another organisation’s data. We may suspend an account that does, and we will say why.

Availability, changes and ending it

The service is provided as it is, without a warranty of uninterrupted availability — it is young, and pretending otherwise would be the first dishonest sentence on it. We may change or discontinue parts of it; where a change removes something you rely on, we would rather tell you than have you discover it. You can stop at any time by uninstalling the App or asking us to close your account. What uninstalling does and does not remove is set out on Privacy, including that it does not by itself erase your history.

Which law applies

These terms do not impose a governing law on you. MLReps is open to anyone anywhere, and naming one country's courts would mean asking most of the people who use it to accept a forum they have never heard of in order to use something free. The law where you are applies, and nothing in these terms takes away a right you have there — where your own consumer law gives you something these terms do not, your own law is the one that counts.

That cuts both ways, so it is worth saying plainly: it also means neither of us has agreed in advance where a dispute would be heard. For something young, with no warranty of availability and with amounts this small changing hands, we think that is the right trade — and if it ever changes, it changes with notice and not retroactively.

Liability

To the extent the law that applies to you allows it, our liability for any claim arising out of your use of MLReps is limited to the amount you have actually paid us in the twelve months before the claim. Where you have paid us nothing, that is nothing. It is stated plainly rather than buried, and it is the only limit we ask for.