Will It Vibe?Analytics present with no consent gate (heuristic)
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
Analytics/tracking code (gtag/ga/fbq/analytics.load/mixpanel.init) is present but no cookie-consent or consent-management code/library was found anywhere in the repo. Heuristic: consent handling can live outside what this scan reads.
Why it matters
Loading Google Analytics, Meta Pixel, Mixpanel, or Segment before the visitor has made a cookie/tracking choice is a common way sites end up out of compliance with GDPR, the ePrivacy Directive, and similar consent-based privacy laws, which generally require consent before non-essential tracking scripts run. This finding is a heuristic: it means this scan could not find any consent-management code or library anywhere in the repository, not that no consent mechanism exists. It is worth a manual check even when the tool is confident, since consent handling sometimes lives in a CMS, tag manager, or third-party config this scan cannot see.
How to fix it
Add a consent banner that blocks analytics/marketing scripts from loading until the visitor accepts, using a library such as CookieConsent, Osano, Cookiebot, or OneTrust, or a tag-manager-based consent mode. Wrap the analytics initialization code so it only runs after consent is granted, and keep essential/functional cookies separate from marketing ones so you are not asking consent for cookies that do not need it. Confirm your privacy policy describes what is tracked and lets visitors withdraw consent later.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo