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

fix(review): explain-change artifact medium should look up repo visibility itself

Abierto
  • ¿Algo no está bien?
#6,951 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #7731 de @melodic-automation-lanes — fusionado

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, javascript
Área
security, tooling

Línea de trabajo

Start with the visibility lookup that publish-hosted.mjs gained in #6783, which uses gh repo view with a host check, and find where the artifact medium's publish gate takes its visibility from the model. Route the artifact gate through the same verified lookup, using REST in cloud sessions as #6750 requires. Done when both media gate on the same verified value and no model-supplied visibility reaches either upload.

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

Descripción

needs-human needs-triage

explain-change's publish gate for the hosted medium now resolves repository visibility itself (#6783, closing #6748): no model-supplied visibility reaches the hosted upload. The artifact medium still takes visibility from the model's own reading of the repository.

Problem

On the artifact path, a private repository can be treated as public when the model misreads its visibility. The worst case is a private claude.ai Artifact (default-private), so the leak risk is lower than the hosted case #6748 fixed, but the gate's input is still untrusted.

Proposed fix

Reuse the visibility lookup that publish-hosted.mjs gained in #6783 (gh repo view with the host check) for the artifact path's gate input, so both media gate on the same verified value.

Related

  • #6748, #6783 (hosted-medium fix)
  • #6749 (stale hosted sidecar), #6750 (GraphQL in cloud sessions: the lookup must use REST there)
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
3 h 42 min
PR fusionados (30 d)
938

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 melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.