Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Impersonation: io.github.jimmybr-PDX/rugradar copies an existing product's name and description (RugRadar)

Abierto
  • ¿Algo no está bien?
#1,708 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
backend

Línea de trabajo

This is a moderation and impersonation dispute about a published listing, not a code change, and the payload names no files, tests or entry points. A newcomer cannot finish it by editing the repository. It needs a registry maintainer to review the listing and decide on removal under the project's dispute process. Done means a maintainer has ruled on the report, not that a patch has merged.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Impersonation report

Hi team, I need to report a listing that appears to impersonate an existing product published in this registry.

Our product (prior use):

  • RugRadar, a free token-safety / honeypot checker, live at https://rugradar-dun.vercel.app
  • Publicly launched 12 Oct 2026 (launch post: https://x.com/The_Real_EJC/status/2109675509726450112)
  • Registered in this registry since 6 Oct 2026 as io.github.Darkjay123/rugradar v1.0.0 (we marked that version deleted today while consolidating into an ownership-verified domain namespace; publish timestamp visible in registry history)
  • Canonical entry now: app.vercel.rugradar-dun/rugradar-mcp (status: active, ownership verified via the HTTP challenge on rugradar-dun.vercel.app)

The listing at issue:

Why we believe this is impersonation: the name ("RugRadar"), title, and product description ("rug-pull, token-safety and honeypot risk checks") closely mirror our product and wording, and the listing was published after both our 6 Oct registry registration and our 12 Oct public launch, pointing at an unrelated endpoint and repository, and monetizing per call. To anyone (or any agent) browsing the registry, this entry reads as our product. It is not.

Request: could the maintainers review io.github.jimmybr-PDX/rugradar for impersonation and remove it, or advise the correct process for this kind of dispute? Happy to provide any additional evidence (launch archives, registry history timestamps).

Thanks.

Lenguaje dominante
Go
Estrellas
7.3k
Forks
1k
Merge medio
3 d 14 h
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/registry

Todos los issues de modelcontextprotocol/registry

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.