Anyone else get a vague GitHub shakedown notice?
Inquiry Regarding a Suspicious GitHub Billing Notice
From: Greg Troxel (gdt at lexort.com)
Date: Friday, July 10, 2026, 09:17:56 PDT
Subject: [QGIS-Developer] anyone else get a vague github shakedown notice?
Executive Summary
Greg Troxel has received a notification from GitHub threatening to initiate billing. After checking his paid plans, reviewing his billing info, and evaluating his current organization memberships, he is now questioning if his association with QGIS is the trigger.
Context & Background
Greg has maintained a GitHub account for a significant duration. However, he emphasizes two critical points:
- He has never subscribed to a premium plan.
- He has never provided GitHub with any payment or billing details.
Recently, he distanced himself from several defunct organizations as he grew weary of the increasing focus on AI integration and paid service tiers.
The Notification
A few days ago, Greg received an email that appeared legitimate (delivered via sendgrid and verified with a GitHub DKIM signature).
Notice Snippet: "You're receiving this because your organization is using the GitHub Code Quality public preview. As we shared on June 16, Code Quality moves to general availability on July 20, 2026."
The email outlines the transition from a preview phase to a paid model.
💰 Pricing Structure
The cost for "Code Quality" is calculated as a base fee combined with usage-based metrics.
| Component | Billing Method | Coverage |
|---|---|---|
| Per-committer license | $10 / active committer / month | Enterprise access: findings, scoring, Rulesets, Security Overview, and governance |
| AI-powered usage | Usage-based (AI Credits) | Copilot code reviews, AI detection, and Autofix generation |
| Deterministic analysis | GitHub Actions minutes | CodeQL-powered reliability and maintainability scans |
The total monthly cost can be represented as: (Where is the number of active committers on enabled repositories)
🛠️ Preparation Steps
GitHub suggested the following actions to avoid unexpected charges:
- Contact a GitHub or Microsoft account representative.
- Utilize the pricing calculator to model potential costs.
- Audit repositories to decide which should keep Code Quality enabled.
- Disable Code Quality before July 20 to ensure no charges are incurred.
The Discrepancy
The email contained a confusing footer stating:
You are receiving this because you’re a part of GitHub Sponsors.
Greg's Response:
- "I am not enrolled [in Sponsors], and I have not sponsored anyone."
Analysis of the Situation
Final Questions for the Community
Greg is seeking input on the following:
- Is the QGIS organization utilizing "Code Quality"? If so, could his activity (cloning, filing issues, etc.) have flagged him as an "active committer"?
- Is this simply a technical glitch/confusion on GitHub's end, or is it a more "underhanded" billing tactic?
- Is anyone else in the developer community concerned about receiving surprise invoices?
Related Threads:
[QGIS-Developer] Coming soon: QGIS Plugins Website v4.0.0
Image: GitHub's branding associated with the notice.