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

Request for private security reporting channel

Abierto
#359 1 comentario 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
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
security

Línea de trabajo

The issue names no source file, test, or entry point; begin with the repository's existing security guidance and review how private reports are currently requested. Done means maintainers provide or document an approved private reporting channel without exposing vulnerability details in this issue.

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

Descripción

bug desktop needs-triage
Product or interface

Desktop app

Version

0.5.4

Platform

Windows

OS version and architecture

Windows 11 x64

Issue area

Other

Desktop log upload ID (optional)

No response

Steps to reproduce

I found multiple reproducible security issues in the current MiniMax Code source preview while performing external security testing.

I have minimal synthetic reproductions, regression tests, and redacted evidence prepared, but I do not want to disclose vulnerability details in a public issue.

Please provide the appropriate private reporting channel so I can share the findings responsibly.

Expected and actual behavior

Expected: A private security reporting channel should be available for disclosure of vulnerability details.

Actual: The repository security guidance directs reporters to request a private channel when private vulnerability reporting is unavailable. I am opening this issue only to request that channel and am intentionally withholding vulnerability details from the public issue.

Redacted error summary
Multiple reproducible security findings are ready for private disclosure. No credentials, real user data, destructive actions, or third-party infrastructure were used during testing.
Screenshots

No response

Before submitting
  • I have searched existing issues.
  • I have included my version and removed sensitive information.
Lenguaje dominante
TypeScript
Estrellas
2k
Forks
259
Merge medio
14 h 20 min
PR fusionados (30 d)
56

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 MiniMax-AI/minimax-code

Todos los issues de MiniMax-AI/minimax-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.