SEC crew findings by severity, with remediation status, per order.

There is no backend route behind Security Review. The Hub cannot read this report, so this page shows nothing rather than showing a sample of what it might one day contain. It is not reporting an empty fleet, and any figure it displayed would be invented.

Until BUG-MSO-2026-0731 this page rendered a hard-coded sample under a “demo layout” banner. The sample is gone. The reader, the endpoint and the real layout are specified in PLAN-PLN-MSO-2026-0726 and land in its Voyage B.

• .mso/reports/security/SEC-*.mdA SEC crew’s own review of one order. Free-form prose; the verdict is not machine-readable in every file.
• .mso/reports/security/REVIEW-*.mdOutput of `mso security scan`. The counts in these files are known to be heavily inflated by false positives — they are scanner runs, not a risk posture.
• mso security scan --jsonRun the scanner yourself for a current answer, rather than reading an archived run.