Compétences golang-samber-slog

📦

golang-samber-slog

Name: golang-samber-slog
Author: samber

v1.1.2 Révision du contenu r1 Risque moyen ⚙️ Commandes externes🌐 Accès réseau⚡ Contient des 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.

Prend en charge: Codex Code(CC)

📊 70 Adéquat

Maintain this Skill? Claim it 📊 70 Adéquat

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/samber-golang-samber-slog.md manifest signé GET /api/skills/samber-golang-samber-slog/manifest lockfile signé GET /api/skills/samber-golang-samber-slog/lockfile

Tester

Utilisation de « golang-samber-slog ». Why do error records reach both PagerDuty and Slack in my Router?

Résultat attendu:

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

Utilisation de « golang-samber-slog ». Where should sampling and PII formatting appear in my pipeline?

Résultat attendu:

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

Utilisation de « golang-samber-slog ». Why are buffered Loki records missing during shutdown?

Résultat attendu:

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

Audit de sécurité

Risque moyen

v1 • 06/09/2026 Ouvrir le rapport versionné

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.

Fichiers analysés

1,341

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Préoccupations de sécurité confirmées (1)

Moyen

SKILL.md:174 references/http-middlewares.md:57-67 references/http-middlewares.md:85-94 references/http-middlewares.md:112-121 references/http-middlewares.md:141-150

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.

Facteurs de risque

⚙️ Commandes externes (50)

🌐 Accès réseau (8)

references/backend-handlers.md:171 references/backend-handlers.md:202 references/backend-handlers.md:171 SKILL.md:12 SKILL.md:63 SKILL.md:64 SKILL.md:65 SKILL.md:234

⚡ Contient des scripts (1)

references/pipeline-patterns.md:206-212

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

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

Badge 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)

Badge 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>

Carte intégrable

<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>

Citations académiques (APA · BibTeX · CFF)

Citation 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

Citation 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"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

100

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces 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.

Bonnes pratiques

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.

Éviter

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.