Skip to content

Store each entry's repo ID to stop name-squat takeovers #36

Closed

Description

@jamesconwaydev

Entries are keyed by owner/name. Say an owner deletes their account. Someone registers the same username, creates a repo with the same name, and the health check happily follows it. The listing, and every Like it earned, now points at a stranger's repo.

GitHub gives every repo a numeric ID that never changes and is never reused. If we save it when an entry is accepted and compare it on every health check, a squatter can't inherit anything.

Done when new entries store repo_id, existing entries are backfilled, and a mismatched ID sends the entry to needs-review instead of updating it.

Activity

  1. added
    priority: highFix this before the next release
    area: dataentries.json and the files on the stats branch
    area: securityAnything someone could use to game the list or hurt its users
    on Nov 6, 2026
  2. updated Effort M, Priority High and Area Security on Nov 6, 2026
  3. jamesconwaydev commented on Nov 6, 2026

    @jamesconwaydev
    CollaboratorAuthor

    Done in #194. Every entry now stores its repo ID. The health check compares it, and a different repo turning up at a listed name gets a removal notice and a review issue instead of the entry. The hourly sync keeps the old card and holds the entry out of Trending meanwhile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: dataentries.json and the files on the stats brancharea: securityAnything someone could use to game the list or hurt its userspriority: highFix this before the next release

    Fields

    Area

    Security

    Priority

    High

    Effort

    M

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions