Trust & Proof: npm – Signal Evidence & AI Readability

npm

(https://npmjs.com) 📸 Data Snapshot: May 30, 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.
15 Impact Weight: 20 / 100
75% Reputation

The site reports a review_count of 0 and a proof_links_count of 0, indicating a total absence of trust signals. No trust_theatre_flag was triggered because there are no reviews to verify or falsify, effectively hiding the site from trust-based forensic analysis. The lack of external proof paths, such as links to documentation or case studies, results in a maximum penalty for proof path absence. Verification of the company’s claims is impossible through the provided data as no outbound validation exists.

The ratio of verifiable evidence to unsubstantiated claims is 0:0, as neither exists on the served page. The site provides zero instances of specific proof points, such as technical specifications, dated results, or named frameworks. The absence of any links to third-party review scores or security certifications leaves the site with a proof density of zero. This total lack of evidence suggests a site that is currently providing no substance to the end user.

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