Security extension for the Copilot App [Public Preview]

Abierto
#1,356 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
10/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
github
Área
security

Línea de trabajo

The issue describes a security canvas in Copilot App and CLI, opened with /security, that brings assigned alerts, campaign work, and prioritized security items into one inbox. It does not identify implementation files, tests, or a specific change to make; the first step would be to find the project and entry points for the Copilot App and CLI security experience. Done would mean delivering the described experience, but the issue does not specify acceptance criteria.

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

Descripción

cloud Public Preview Shipped
Value Prop

You can now view and act on your security work directly inside GitHub Copilot — no browser tab-switching required. Type /security in Copilot App or CLI to open a security canvas that brings your assigned alerts, campaign work, and prioritized security items into a single, unified inbox. Filter, triage, and work through security findings organized by risk and relevance, right where you already code.

Expected Outcome

Security alerts today are scattered across scanner-specific pages, making it hard for developers to know what to fix first. By surfacing prioritized security work inside Copilot App and CLI, developers can discover and address vulnerabilities without breaking their flow. The goal is to reduce context-switching and help teams close security gaps faster by meeting developers where they already work.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
9k
Forks
1.8k
Métricas de merge de PR
Sin PR fusionados en 30 d

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 github/roadmap

Todos los issues de github/roadmap

Issues similares

Más issues de Security

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.