技能 golang-samber-slog

📦

golang-samber-slog

Name: golang-samber-slog
Author: samber

v1.1.2 內容修訂 r1 中風險 ⚙️ 外部命令🌐 網路存取⚡ 包含腳本

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.

支援: Codex Code(CC)

📊 70 尚可

Maintain this Skill? Claim it 📊 70 尚可

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

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.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/samber-golang-samber-slog.md 已簽名 manifest GET /api/skills/samber-golang-samber-slog/manifest 已簽名 lockfile GET /api/skills/samber-golang-samber-slog/lockfile

測試它

正在使用「golang-samber-slog」。 Why do error records reach both PagerDuty and Slack in my Router?

預期結果:

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

正在使用「golang-samber-slog」。 Where should sampling and PII formatting appear in my pipeline?

預期結果:

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

正在使用「golang-samber-slog」。 Why are buffered Loki records missing during shutdown?

預期結果:

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

安全審計

中風險

v1 • 2026/9/6 開啟版本化報告

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.

已掃描檔案

1,341

分析行數

複核項目

已忽略的誤報

已確認的安全問題 (1)

中

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.

風險因素

⚙️ 外部命令 (50)

🌐 網路存取 (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

⚡ 包含腳本 (1)

references/pipeline-patterns.md:206-212

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

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

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)

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>

嵌入卡片

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

學術引用 (APA · BibTeX · CFF)

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

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"

Skillstore 評分

評分依據證據置信度: 中

架構

100

可維護性

內容

社群

規範符合度

你可以打造什麼

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.

試試這些提示

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.

最佳實務

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.

避免

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.