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

🔒 [IBM OSPO Security Notification] — IBM/platform-services-node-sdk

Abierto
#366 14 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
javascript
Área
ci-cd, security

Línea de trabajo

Start with the Code Scanning alerts listed in this issue: js/clear-text-logging and the four actions/missing-workflow-permissions findings. The payload names no source files, workflow files, tests, or entry points, so locate the alert details in Code Scanning before making changes; done means all listed alerts are resolved.

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

Descripción

security

🔒 [IBM OSPO Security Notification] — IBM/platform-services-node-sdk

Action required: Remediate the alerts listed below before their SLA deadline.
This issue will be closed automatically once all alerts are resolved.

SLA policy: critical = 7 days, high = 30 days, medium = 90 days, low = no deadline.
Alerts at or above medium severity will trigger a warning comment before the deadline and
repo archiving if unresolved. Low-severity alerts are tracked here for visibility only —
they will never trigger warnings or archiving.

💡 Tip: To have Dependabot automatically open fix PRs for dependency alerts, enable
Dependabot security updates in your repo settings:
Settings → Advanced Security → Dependabot security updates → Enable.

📖 New to this issue? See the Security Issue Guide for a full explanation of what this issue means and what you need to do.

Attention: (no direct admin collaborators assigned to this repo — please add an admin to receive security notifications)

Dependabot Alerts
Severity CVE/GHSA Package Affected Patched Deadline Fix PR
🟠 high CVE-2026-93748 http-cache-semantics <= 4.2.0 — 2026-11-26 —
🟠 high CVE-2026-111755 follow-redirects >= 1.16.0, < 1.16.1 1.16.1 2026-11-20 —
🟠 high CVE-2026-111756 follow-redirects >= 1.16.0, < 1.16.1 1.16.1 2026-11-20 —
🟡 medium CVE-2026-41907 uuid < 11.1.1 11.1.1 2027-01-25 —
🟡 medium CVE-2026-101910 ip-address >= 10.2.0, <= 10.5.0 10.5.1 2027-01-25 —
🟡 medium CVE-2026-101912 ip-address <= 10.7.0 10.7.1 2027-01-25 —
🟡 medium CVE-2026-101913 ip-address <= 10.5.0 10.5.1 2027-01-25 —
🟡 medium CVE-2026-102277 brace-expansion >= 4.0.0, < 5.0.12 5.0.12 2027-01-25 —
Code Scanning Alerts

No open code scanning alerts.

Secret Scanning Alerts

No open secret scanning alerts.


Lenguaje dominante
JavaScript
Estrellas
7
Forks
59
Merge medio
1 d 8 h
PR fusionados (30 d)
2

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 IBM/platform-services-node-sdk

Todos los issues de IBM/platform-services-node-sdk

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.