Terms
What you are buying, what we promise, and what we deliberately do not claim. Written to be read rather than skimmed past.
Last updated 6 August 2026
Who you are dealing with
This service is operated by RallyMate Pty Ltd, trading as Struck Code, at struckcode.com. In these terms, we and us mean that company, and you means the person or company that buys a report.
What you are buying
You connect one repository, read only, and we produce three things:
- A report: findings with evidence, a plain-English note on what each one means for a buyer, and a remediation list ranked by how much each fix would move your grade.
- A certificate: a graded scorecard bound to one commit, with a public verify page you can attach to a listing.
- One fix-and-rescan within 60 days, which issues a new certificate version. Additional re-scans are $99 each.
The price is $299. The fee is the same whatever grade your code receives.
Before you pay anything you get a free preview, roughly a third of the report, produced by running the real analysis against your real repository. The preview is how you check that the work is worth buying.
What we assess, and what we do not
We assess code and the machinery around it. Whether advertised features exist and are reachable. Whether tests run. Whether the paywall is enforced on the server rather than in the interface. Whether the licences permit a commercial sale. Whether live credentials sit in the repository or its history.
We do not verify revenue, MRR, churn, customer counts, or any other financial or business claim, and we make no statement about them. Source code cannot show you those things, and pretending otherwise would undermine the only thing the certificate is good for. This boundary is printed on the certificate itself.
Our methodology is published in full, including every check, what each one can raise, and how points move. It is versioned, and every certificate names the version that produced it.
A report describes one commit at one moment
Your grade is a property of a specific commit and file tree. Code changes after that point are not covered, and the verify page shows how old a certificate is and labels it stale after 180 days.
This is a point-in-time, best-effort assessment produced by automated analysis. It is not an audit, not insurance, not a warranty, and not a guarantee that your code is free of defects or vulnerabilities. Automated analysis misses things. A good grade means our checks found little to raise, not that nothing exists to find. Anyone relying on a certificate, including a buyer, should understand it on those terms.
We do not provide legal, financial, tax, or investment advice, and nothing in a report or certificate is a recommendation to buy or sell a business.
Your side of it
- You own the repository you submit, or you have permission from whoever does to have it analysed. This one matters, because we act on your instruction.
- The claims you confirm at intake are your assertions about your product, not ours. We verify them against the code and report what we find. We freeze the confirmed set so that certified claims cannot quietly diverge from your live listing.
- You will not tamper with the analysis. Suppression files and ignore configuration added to defeat scanning are themselves a finding, and egregious cases are grounds for revoking a certificate.
- You are responsible for keeping your account credentials secure.
The certificate
A certificate is always issued once you pay, whatever the grade. Publishing it is your choice, and it is all or nothing per version: you cannot publish some dimensions and hide others. An unpublished certificate sits behind an unguessable link and returns nothing to the public.
We may revoke a published certificate in four situations, and we will tell you first and give you seven days to respond:
- Certified claims materially differ from your live listing.
- The analysis was tampered with.
- An undisclosed material fact comes to light, such as a copyright claim over the code or a dispute about who owns it.
- A buyer dispute is upheld.
After that the verify URL permanently shows the certificate as revoked, with a reason category and a date. We publish a log of revoked certificate ids and categories, and nothing else. Withdrawal following a refund is a separate thing and never appears in that log. See the refund policy.
Your code stays yours
You keep every right in your code. You give us permission to analyse it for the purpose of producing your report and certificate, and nothing further. We do not train models on your code, we do not resell or aggregate anything derived from it, and we destroy every copy of your source when the analysis finishes. What we keep is the report: findings, short evidence excerpts, measurements, and hashes.
Your code and your report are confidential, in both directions, and this obligation continues after you stop using the service. The full detail is in how we handle your code.
Limits on what we owe you
Nothing here limits liability that cannot lawfully be limited, including under the Australian Consumer Law where it applies to you.
Subject to that, our total liability to you for anything arising out of this service is limited to the greater of the fees you paid us and $299. We are not liable for lost profits, lost sales, a deal that does not complete, a price you accepted or rejected, or any indirect or consequential loss.
A certificate is information, not advice, and decisions made on the strength of one are the decision-maker's own. If you are a buyer relying on a certificate rather than the seller who bought it, you have no contract with us and we owe you no duty in respect of it.
Ending it
You can close your account at any time. We may suspend or close an account that breaches these terms, in which case any unused re-scan credit is refunded pro rata.
Law and disputes
These terms are governed by the laws of Victoria, Australia, and the courts there have jurisdiction. Talk to us first. Most things that look like a dispute are a misunderstanding about what a grade means, and we would rather explain it than argue about it.
Changes
We may update these terms. The version in force for your report is the one published when you paid, and we keep the date at the top current. Material changes are emailed to account holders.
Questions about any of this go to contact.