Someone delivered software to you and included a Mantyl project passport. This page explains what that document is, what it proves, and how to check it yourself. You do not need an account, and there is nothing here to buy.
A project passport is a structured record of what was delivered: what the software contains, how to set it up, what decisions shaped it, what was checked, and what remains unknown. It was generated by a tool, reviewed by the person who built your project, and every statement in it is labelled with where it came from. It is organised evidence, not marketing.
The honesty of a passport lives in its labels. A claim marked verified was proven by actually executing something: the build ran, the tests passed, in a clean isolated environment. Repository confirmed means the code itself shows it, and agent reported means an AI coding assistant said it during development but nothing has independently confirmed it: treat those as leads, not facts. A claim marked contradicted is the tool telling you something the builder said does not match what the code shows, and unknowns are open questions the passport surfaces instead of hiding. A passport with visible uncertainty is working as designed; one that claimed everything was perfect would deserve suspicion.
If the passport carries the MANTYL VERIFIED mark, the delivered source was uploaded to infrastructure the builder does not control, proven byte-for-byte identical to what the passport describes, and every recorded check was re-executed there from scratch. The result is signed, the signature binds the exact commit and passport, and the hosted page re-checks that signature every time it renders. What the mark does not do is judge quality: it proves the recorded checks reproduce, exactly as stated, no more and no less.
You do not have to take the passport’s word, or ours. With the delivered repository on your machine and Node installed, run one command in the project folder:
If someone changed a single file after the passport was generated, this names the file. That is the point of the document: you can hold it against the delivery, any time, without trusting anyone.
A passport describes and proves the software itself. It does not transfer the things around the software, so before you consider a handover finished, ask your builder separately about ownership of the repository and its history, rotated credentials and who holds admin access to hosting, domains and third-party services, operational runbooks for when something breaks, and any ongoing support arrangement. A good passport plus those answers is a complete handover; the passport alone is the provable half.