The end of the CV.
Acquispect puts evidence in place of claims. The Proof Engine checks real work — your public Git repository — and keeps the result with its audit log under a public verification link.
Git forensics · Roslyn · .NET 10 · Orleans
// THE PIPELINE
First objective facts from Git and the code — then the AI.
// STAGE A
Ghostwriter detector
Forensic .git analysis: how the changes are spread across the authors, whether code was imported in one big block and whether the repository is a fork; also the share of commits that themselves state an AI agent's part. Plain C#, no AI costs.
// STAGE B
Safety Check
Patterns of leaked secrets in the working tree and the history, including the providers' public formats, risky calls in C# (Roslyn), TypeScript/JavaScript, Python, Java/Kotlin and Go, test files and the tech stack with shares. Also the dependencies from lock files, checked against known vulnerabilities (OSV.dev) with their severity, and, without points, project signals after the OpenSSF Scorecard, the CI result and the branch protection.
// STAGE C
Panel of Experts
Five AI personas (tech lead, security, performance, architecture, craft) each assess an excerpt of the code on their own; their scores make up 60 % of the verdict. If the panel does not run for a check, for instance because the monthly budget is used up, the verdict rests on Stages A and B alone and goes no higher than “Lean”.
See an example result → a real check of a public repository: verdict, stages, audit log
// FOR DEVELOPERS
Show what your code proves.
The check is free and needs no account. The result stands with its audit log under a public link you can share, and as a signed credential (W3C Verifiable Credential) to download, which anyone can check with the public key from acquispect.com's did:web document, without asking us. From “Hire” upwards there is a badge for your README.
For developers →// FOR COMPANIES
Evidence instead of a CV.
A candidate shares the verification link of their repository; you see the verdict, the stages and the audit log instead of a claim. Paid checks for companies are planned.
For companies →// FAQ
Frequently asked questions
What does Acquispect check?
The Proof Engine clones a public Git repository and reads it without running its code. Stage A reads the Git history (how the authorship is spread, code dumps, forks, the AI share of the commits), Stage B looks for patterns of leaked secrets in the working tree and the history, including the providers' formats, risky calls in C#, TypeScript/JavaScript, Python, Java/Kotlin and Go, test files and known vulnerabilities in the dependencies with their severity (OSV.dev) and names, without points, project signals, the CI result and the branch protection. In Stage C five AI personas assess an excerpt of the code.
What does the check cost?
Nothing for developers, and it needs no account. For companies a price per verification is planned; nothing can be booked today.
Which repositories can I check?
Public repositories on github.com, gitlab.com, bitbucket.org and codeberg.org.
How long does a check take?
Five minutes at most. The page shows the stages as soon as they are done.
What is the result?
A verdict with its audit log under a public verification link you can share, and the same result as a signed credential to download. From “Hire” upwards there is a badge for your README. If the expert panel does not run for a check, the recommendation goes no higher than “Lean”.
Does the result prove that I wrote the repository?
No. The verdict is about the repository, not about the person who submits it. Binding it to the person is planned.
// GUIDES
Latest guides
- Technical assessment of developer work
- Regression Test vs Integration Test Explained
- How to assess a software developer CV properly
- European Digital Identity: explained simply
- Release Management: Why It Matters for Code Quality
- Reading Pull Requests: What They Reveal About Developers
- Phone interview questions for developers
- Issue Tracker: What They Show About Developers
- Digital identity explained simply
- Substantiate Your Developer Portfolio with Real Code
- Code Review: How to recognise good reviews
- Detecting Plagiarism: How to Spot Someone Else’s Code