Trust & Proof: ReactOS Project – Signal Evidence & AI Readability

ReactOS Project

(https://reactos.org) 📸 Data Snapshot: May 25, 2026
Trust & Proof — The Lens

Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.

Trust & Proof Verifiable evidence vs. Trust Theatre.
19 Impact Weight: 20 / 100
95% Reputation

Trust theatre is virtually non-existent. The site eschews generic ‘Trusted by’ logos and G2/Capterra badges in favor of direct links to development tools. While the meta-data shows a review_count of 5 on the contributing page without linked verification, the abundance of functional proof paths (GitHub, Jira, Mattermost) offsets any potential for theatre.

Proof density is high. The ratio of evidence (30+ specific apps in Gallery, GitHub repo links, Jira bug tracker) to assertions is heavily weighted toward substance. The presence of a live activity feed [H3] Live Activity provides real-time proof of project vitality.

Trust & Proof is read by weighing trust language against real verification. Below is the page-by-page tally of review mentions and external proof links, then the schema markup that may (or may not) declare verifiable ratings and identity proof.

🛡️ Trust Signals — reviews, proof links, trust-theatre check
5Review mentions (all pages)
5External proof links (all pages)
PageReviewsProof links
/ (home) 0 1
/gallery/ 0 1
/contributing/ 5 2
/getbuilds/ 0 1
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)
/gallery/ — no schema detected (entity gap)
/contributing/ — no schema detected (entity gap)
/getbuilds/ — no schema detected (entity gap)