NEXUS VERIFYIndependent software checks

Nexus Verify · Teardowns & research

Teardowns & research

Write-ups from real checks — what was tested, what was found, and the evidence behind it. Everything here traces to a public artifact: a signed registry entry, a published report, or the run record itself.

See pricing →

Index

Published so far

The deletion cookie that forgot Secure

Teardown · November 11, 2026. A frozen checking instrument over 230 Java files (JPetStore-6 and Spark) in 46 seconds: 16 findings — 1 real fix, 1 informational, and 14 not-a-defect, each with its reason printed. The point of a teardown here is the dispositions, not the count.

Read the teardown →  ·  The full sample run →

What a report looks like

Sample run. A complete sample check, published in full — findings, dispositions, and evidence, in the same shape a customer receives. Read it before you ever pay for one.

See the sample run →

Verdicts, published

The signed registry. Every judged verdict lands in the registry with its evidence — the failures at the same prominence as the passes, each entry digest-linked to its campaign record.

Read the evidence →  ·  Check the live signed registry →

The attack lab

Measured record. One of the twenty labs in every certification campaign exists to attack the work. Its published record: 5 probes held and 3 planted defects caught in its first full campaign, 10 of 10 hostile cases held against the live verification service itself, and a PASS in all five registry verdicts — stated with its grade: the signed narrative attack report has not been issued yet.

Read the attack-lab record →

The proving ground

Capability. Beta testing run as evidence: a declared cohort works declared journeys, every execution is recorded, and no result counts until every failure carries a disposition — fixed and re-tested with the evidence linked, or accepted as a risk under a named sign-off.

Read how the proving ground works →

How to read these

What these pages are

  • Every number traces to an artifact — a registry entry, a report, or a run record you can open.
  • Instruments are named with their scores on their face, including the weak ones. A check is a measurement, not a promise that software is bug-free.
  • There are no customer stories here yet, and this page will say so until there are. When customers exist and agree to be named, their stories will appear with the same evidence standard.

Start with the intake

Tell us what you need checked. The quote comes back in writing, and a payment link is sent with your confirmed quote — you pay only after you have seen the final price in writing and accepted it.

Go to the intake form →