[fleizean]

Summary

When a PyPI package lists no GitHub link in its metadata, the repository is now taken from the package description (README), provided the repository is named after the package.

Why

selenium lists only https://www.selenium.dev in project_urls and home_page. Its repository, github.com/SeleniumHQ/Selenium, appears only in the README. The package page therefore showed the website instead of the repository, and release notes were never looked up on GitHub.

Changes

• PyPIService: reads info.description and, when no project link points at GitHub, takes the first GitHub link in it whose repository name matches the package name.
• Names are compared after PEP 503 normalisation (case-insensitive; -, _ and . are equivalent).
• Links to other repositories are ignored. Selenium's README also links mozilla/geckodriver, which must not be picked.
• The existing order (source links, home page, other project links) is unchanged; the description is the last resort.

Notes for reviewers

Cached packages pick up the repository URL on their next metadata refresh. No migration.

Checklist

• The pull request targets develop and is about one thing
• Commit messages follow Conventional Commits (feat(scope): ..., fix(scope): ...)
• CI is green (backend tests, frontend build and tests, dependency gate)
• Schema changes are EF Core migrations generated by the tool, not hand-edited
• A changed backend DTO has its TypeScript twin updated in src/frontend/src/app/core/models
• New dependencies are justified and their lock files are updated in the same commit
• No secrets, tokens or personal data in code, logs or this description
• Code comments are kept to a minimum; the reasoning lives in this description