Release v1.0.2

[ViktorSvertoka]

No description provided.

Generally, to fix this kind of issue you should stop using substring checks on full URL strings and instead parse the URL and examine its hostname (or origin) explicitly, or otherwise compare the canonicalized URL to a trusted set of values. For hosts, this means using new URL(avatarBase).hostname === 'avatars.githubusercontent.com' (or a small whitelist) rather than avatarBase.includes('avatars.githubusercontent.com').

For this specific file, the hasStarred logic is:

const avatarBase = user.avatar?.split('?')[0] ?? '';
const hasStarred =
  stargazerLogins.has(nameLower) ||
  (avatarBase.includes('avatars.githubusercontent.com') &&
    stargazerAvatars.has(avatarBase));

Here, the intention seems to be: if the user’s avatar is a GitHub avatar URL and that URL base is present in the set of known stargazer avatars, treat them as having starred the repo. We can make this robust by (a) parsing avatarBase with the URL constructor, (b) extracting hostname, and (c) checking that it equals avatars.githubusercontent.com. To avoid throwing on invalid URLs, we'll wrap the parse in a try/catch and treat unparsable values as non-GitHub.

We do not need new imports; URL is available in the Next.js/Node/DOM environment used in a Next 13+ app. The minimal change is to replace the avatarBase.includes('avatars.githubusercontent.com') condition with a call to a small helper function inside this file (or an inline try/catch) that validates the hostname. To stay within the provided snippet, we’ll implement this inline in the condition using a try { ... } catch {} expression pattern.

Concretely, we will change lines 72–76 so that hasStarred is computed as:

• Parse avatarBase with new URL(avatarBase)
• Check url.hostname === 'avatars.githubusercontent.com'
• If parsing fails, treat the condition as false.

No other logic will be altered.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
devlovers-net	Ready	Preview, Comment	Feb 22, 2026 11:24pm

[netlify]

✅ Deploy Preview for develop-devlovers ready!

Name	Link
🔨 Latest commit	b3e4e56
🔍 Latest deploy log	https://app.netlify.com/projects/develop-devlovers/deploys/699b902271126000086fa42d
😎 Deploy Preview	https://deploy-preview-359--develop-devlovers.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Too many files!

This PR contains 204 files, which is 54 over the limit of 150.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch develop

---

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.}