Update gh-sponsor-meta.json

[netroutingcom]

Added new sponsor Netrouting.com.

Summary by CodeRabbit

• Chores
  • Added a new sponsor entry to the platform.

[netlify]

👷 Deploy request for tanstack pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	20124f3

[coderabbitai]

📝 Walkthrough

Walkthrough

A new sponsor entry with login netroutingcom is added to the sponsor metadata JSON file, including name, image URL, and link URL fields. No existing entries were modified.

Changes

Cohort / File(s)	Summary
Sponsor Metadata src/utils/gh-sponsor-meta.json	Added new sponsor entry for netroutingcom with associated metadata (name, image URL, link URL).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A sponsor hops in, fresh and new,
With metadata gleaming in morning dew,
The JSON sings with grateful cheer,
netroutingcom is welcomed here! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update gh-sponsor-meta.json' is vague and generic, using only the filename without conveying what was actually changed or why.	Consider a more descriptive title like 'Add Netrouting.com sponsor entry to gh-sponsor-meta.json' that clearly indicates the main change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/utils/gh-sponsor-meta.json`:
- Around line 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.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 60ed0532-7639-4162-a732-9a0c0d13918f

📥 Commits

Reviewing files that changed from the base of the PR and between 004be5c and 20124f3.

📒 Files selected for processing (1)

• src/utils/gh-sponsor-meta.json

[coderabbitai]

⚠️ 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:

• 1: https://netrouting.com/ryzen-3800x-dev-infrastructure-benchmark-128gb-ram-8-cores/
• 2: https://netrouting.com/the-litellm-sulitellm-supply-chain-attack-infrastructure-risk/
• 3: https://github.com/sponsors/tannerlinsley
• 4: https://github.com/tanstack
• 5: https://tanstack.com/partners
• 6: https://tanstack.com/partners?status=active
• 7: https://github.com/natesales/pathvector
• 8: https://github.com/netbirdio/netbird/tree/main/route
• 9: https://github.com/networktocode/netutils
• 10: https://github.com/netravnen
• 11: https://github.com/netnr?tab=followers
• 12: https://github.com/netnr?tab=following
• 13: https://github.com/netdotwork
• 14: https://github.com/tannerlinsley?tab=sponsoring

---

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.