Trust & Proof: Web3.js – Signal Evidence & AI Readability

Web3.js

(https://web3js.org) 📸 Data Snapshot: May 24, 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.
8 Impact Weight: 20 / 100
40% Reputation

The site exhibits high trust theatre with 12 reviews listed on the homepage but 0 verifiable proof links to external sources. The trust_theatre_flag is true because while specific entities like Chainstack and DeFi Saver are named in H3 tags, there is no digital path to verify these testimonials or the projects mentioned. The reviews are effectively isolated text blocks without third-party validation.

The ratio of internal technical proof (code snippets and specific module support) is high, but external proof is non-existent. With a proof_links_count of 0 across all pages, the site relies entirely on the user’s prior knowledge or willingness to trust the text. The presence of named client quotes provides ‘soft’ proof, but the lack of outbound links to GitHub or documentation from those clients limits the density of verifiable evidence.

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
16Review mentions (all pages)
0External proof links (all pages)
PageReviewsProof links
/ (home) 12 0
/plugins/ 4 0
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)
/plugins/ — no schema detected (entity gap)