How This Briefing Works
This dossier opens with key findings, then maps the gap between what Github discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.
At a Glance
across 2 sites
vendor fires before consent
Briefing
Developer platform with embedded analytics/tracking for repository widgets, login integrations, or marketplace features. Pre-consent script loading violates ePrivacy requirements despite legitimate platform functionality. Risk: consent violations for tools with clear business necessity but poor privacy implementation.
What This Means For You
Engineering teams inherit consent liability for essential developer tooling with legitimate business purpose. Legal teams must defend privacy violations for platform that provides clear value (unlike pure surveillance vendors). Compliance teams face regulatory scrutiny for technical implementation, not business necessity.
Risk Channel Breakdown
Distorts attribution data
Feeds competitor intelligence
Expands attack surface
Loads platform integration scripts before consent banner interaction. While Github provides essential developer functionality, pre-consent initialization violates ePrivacy Directive Article 5(3) regardless of business necessity.
Threat Indicators
Runtime-observed (BTI-C)
Ignoring CMP signals
Per-code narrative explanations of what each detected behavior means for your organization
Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →
Claims vs. Reality
BLACKOUT analyzed Github's public claims against observed runtime behavior and identified 1 contradiction.
Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →
What To Do
3 for current users · 3 for evaluators
contractual leverage points
Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →
Supply Chain & Pairings
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →