Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/utils/gh-sponsor-meta.json
Original file line number Diff line number Diff line change
@@ -1,4 +1,10 @@
[
{
"login": "netroutingcom",
"name": "Netrouting.com",
"imageUrl": "https://netrouting.com/wp-content/uploads/2026/04/netrouting-color.png",
"linkUrl": "https://netrouting.com/"
},
Comment on lines +2 to +7
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Confirm whether the GitHub account login is exactly "netroutingcom" (case-sensitive), and whether that same login appears in TanStack’s GitHub Sponsors list.

💡 Result:

No evidence found that a GitHub account with the exact case-sensitive login "netroutingcom" exists. Searches for github.com/netroutingcom, "netroutingcom" as a GitHub user, and related terms returned no matching user profile. The domain netrouting.com exists and references GitHub in blog posts (e.g., benchmark script on GitHub), but no specific "netroutingcom" account is identified. No evidence that "netroutingcom" appears in TanStack’s GitHub Sponsors list. TanStack sponsors via tannerlinsley GitHub Sponsors page (190 sponsors, list not publicly detailed in results), and tanstack.com/partners page lists partners like Netlify, Neon, but no "netroutingcom" or Netrouting. No mentions in sponsor-related pages or commits.

Citations:


Remove or correct the invalid login value "netroutingcom".

No GitHub account exists with the login "netroutingcom" (searched both case-sensitive and across public GitHub). This entry has no amount field fallback, so it will be silently dropped during processing by sponsors.functions.ts. Either correct the login to match an actual GitHub sponsor, add an amount field to ensure the entry is retained, or remove the entry entirely.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/utils/gh-sponsor-meta.json` around lines 2 - 7, The JSON sponsor entry
with "login": "netroutingcom" is invalid and will be dropped by
sponsors.functions.ts because it lacks a valid GitHub login and no fallback
"amount" field; fix it by either (A) correcting the "login" value to the actual
GitHub username for this sponsor, (B) adding a numeric "amount" field to the
same object (keys "login", "name", "imageUrl", "linkUrl") so it won’t be
filtered out, or (C) removing the entire object if no valid GitHub account or
amount is available; update the entry so downstream code in
sponsors.functions.ts retains or properly identifies this sponsor.

{
"login": "wildfee",
"name": "AI-Text-Humanizer.com",
Expand Down