Habilidades golang-samber-slog
📦

golang-samber-slog

v1.1.2 Revisión del contenido r1 Riesgo medio ⚙️ Comandos externos🌐 Acceso a red Contiene scripts

Build Go Logging Pipelines with samber/slog

Complex Go logging pipelines can duplicate records, lose buffered events, or expose sensitive data. This skill guides composition, sampling, formatting, middleware, routing, and shutdown.

Compatible con: Codex Code(CC)
📊 70 Adecuado

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente
Review the Skillstore skill "golang-samber-slog" from https://skillstore.io/skills/samber-golang-samber-slog.md and its manifest at https://skillstore.io/api/skills/samber-golang-samber-slog/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Pruébalo

Usando "golang-samber-slog". Why do error records reach both PagerDuty and Slack in my Router?

Resultado esperado:

The default Router sends each record to every matching handler. Use FirstMatch and order the error rule before the warning rule.

Usando "golang-samber-slog". Where should sampling and PII formatting appear in my pipeline?

Resultado esperado:

Place sampling first, then apply PII formatting, then route clean records to sinks. Preserve important records with level-aware routing.

Usando "golang-samber-slog". Why are buffered Loki records missing during shutdown?

Resultado esperado:

The Loki client must stop during graceful shutdown. Register its stop operation and allow enough time to flush pending records.

Auditoría de seguridad

Riesgo medio

All 69 static alerts are false positives caused by Markdown, Go syntax, placeholders, documentation links, or benign logging terminology. One medium contextual risk remains because examples enable request-body logging without sensitive-data guidance.

6
Archivos escaneados
1,341
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (1)

Medio
Request bodies may expose sensitive data
Examples enable request-body logging without warning that bodies may contain credentials, tokens, or personal data sent to configured log sinks.
Five examples explicitly set WithRequestBody to true, while the surrounding guidance provides no warning or body-redaction requirement.
Auditado por: codex
Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado
Evaluación de seguridad

Copiar enlace del informe

https://skillstore.io/skills/samber-golang-samber-slog/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Insignia Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-samber-slog/security.svg)](https://skillstore.io/skills/samber-golang-samber-slog?utm_source=security_passport_badge)

Insignia HTML

<a href="https://skillstore.io/skills/samber-golang-samber-slog?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-samber-slog/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Tarjeta para insertar

<iframe src="https://skillstore.io/embed/skills/samber-golang-samber-slog.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Citas académicas (APA · BibTeX · CFF)

Cita APA

samber. (2026). golang-samber-slog security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/samber-golang-samber-slog/audits/1

Cita BibTeX

@techreport{samber-samber-golang-samber-slog-2026, author = {samber}, title = {golang-samber-slog security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/samber-golang-samber-slog/audits/1}, note = {Author version 1.1.2} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "golang-samber-slog security audit report (audit version 1)" version: "1.1.2" type: report authors: - name: "samber" date-released: "2026-09-06" url: "https://skillstore.io/skills/samber-golang-samber-slog/audits/1" identifiers: - type: other value: "skillstore:samber-golang-samber-slog:audit:1" description: "Skillstore immutable audit report identifier"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio
45
Arquitectura
100
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación

Lo que puedes crear

Compose a service logging pipeline

Create a pipeline that samples noise, masks sensitive attributes, and routes records by level.

Standardize HTTP request logs

Configure framework middleware with consistent levels, request identifiers, tracing fields, and filters.

Diagnose production logging behavior

Find dropped records, duplicate routing, latency bottlenecks, and missing shutdown flushes.

Prueba estos prompts

Create a basic pipeline
Create a Go slog pipeline using samber/slog-multi. Send error records to Sentry and all records to standard output.
Add sampling and privacy controls
Add threshold sampling and PII formatting to my existing slog pipeline. Explain the handler order and preserve all error records.
Configure HTTP middleware
Configure slog middleware for Gin with distinct 4xx and 5xx levels, request IDs, tracing fields, and health-check filters. Keep body logging disabled.
Review a production architecture
Review my samber/slog pipeline for duplicate routing, latency, data exposure, fallback behavior, and shutdown loss. Propose tested changes with tradeoffs.

Mejores prácticas

  • Sample early, format sensitive attributes before routing, and define a catch-all route.
  • Benchmark handler latency and test routing with in-memory handlers before deployment.
  • Flush buffered backends during graceful shutdown and verify failures are observable.

Evitar

  • Do not enable request or response body logging without redaction and route exclusions.
  • Do not assume Router stops after the first matching handler.
  • Do not use synchronous Fanout when cumulative sink latency is unacceptable.

Preguntas frecuentes

Which Go versions does this skill target?
It targets Go 1.21 and later because the packages build on the standard log/slog API.
Can it configure multiple logging destinations?
Yes. It explains routing, fanout, failover, and pooling across supported samber handlers.
Does it prevent sensitive data from entering logs?
It provides formatter patterns for selected attributes. Applications must still identify sensitive fields and avoid unsafe body logging.
Does it install Go packages automatically?
No. It can recommend imports and versions, but dependency changes remain part of the project workflow.
Can it validate a production pipeline?
It can review composition and propose tests. Runtime load, backend availability, and package behavior still require direct testing.
Why must buffered handlers stop cleanly?
Buffered handlers may retain unsent records. Their stop or close operation flushes pending data before the process exits.

Detalles del desarrollador

Autor

samber

Licencia

MIT

Versión del autor

v1.1.2

Revisión de Skillstore

r1

Ref.

e5464e662405de6361fdde6b984f9ea865635f64

Actualidad del mantenimiento

8/9/2026

Uso

1 descargas · 0 vistas