스킬 golang-spf13-viper

📦

golang-spf13-viper

Name: golang-spf13-viper
Author: samber

v1.1.2 콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어🔑 환경 변수🌐 네트워크 접근📁 파일 시스템 접근

Configure Go Applications with Viper

Layered Go configuration can fail through incorrect precedence, binding, or decoding. This skill provides focused Viper patterns for reliable setup, testing, and reloads.

지원: Codex Code(CC)

🥉 78 브론즈

Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

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

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/samber-golang-spf13-viper.md 서명된 manifest GET /api/skills/samber-golang-spf13-viper/manifest 서명된 lockfile GET /api/skills/samber-golang-spf13-viper/lockfile

테스트해 보기

"golang-spf13-viper" 사용 중입니다. Why does an environment variable for database.host remain ignored?

예상 결과:

The diagnosis identifies the missing dot-to-underscore key replacer and lists the required prefix, replacer, and automatic binding sequence.

"golang-spf13-viper" 사용 중입니다. How should an optional configuration file be loaded?

예상 결과:

The response distinguishes a missing file from parsing or permission errors, allowing only the missing-file case to continue.

"golang-spf13-viper" 사용 중입니다. How can a service reload configuration without data races?

예상 결과:

The response proposes candidate decoding, validation, synchronized replacement, error logging, and retention of the previous valid configuration.

보안 감사

안전

v1 • 2026. 9. 23. 버전별 보고서 열기

All 97 static alerts are contextual false positives. The matches are documentation syntax, Go tags, evaluation prose, conventional configuration examples, loopback addresses, or transparent upstream links.

스캔된 파일

1,310

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

⚙️ 외부 명령어 (50)

🔑 환경 변수 (5)

evals/evals.json:344 evals/evals.json:349 references/binding-and-env.md:32 references/binding-and-env.md:36 references/sources-and-formats.md:24

🌐 네트워크 접근 (6)

references/sources-and-formats.md:90 references/sources-and-formats.md:90 SKILL.md:12 SKILL.md:31 SKILL.md:32 SKILL.md:190

📁 파일 시스템 접근 (4)

references/sources-and-formats.md:67 references/sources-and-formats.md:38 references/sources-and-formats.md:67 SKILL.md:73

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

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

Markdown 배지

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

HTML 배지

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

임베드 카드

<iframe src="https://skillstore.io/embed/skills/samber-golang-spf13-viper.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-spf13-viper security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/samber-golang-spf13-viper/audits/1

BibTeX 인용

@techreport{samber-samber-golang-spf13-viper-2026,
  author = {samber},
  title = {golang-spf13-viper security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-spf13-viper/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-spf13-viper security audit report (audit version 1)"
version: "1.1.2"
type: report
authors:
  - name: "samber"
date-released: "2026-09-23"
url: "https://skillstore.io/skills/samber-golang-spf13-viper/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-spf13-viper:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

100

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Configure a Go Service

Create layered file and environment configuration with predictable precedence and optional config files.

Connect Cobra Flags

Bind CLI flags before execution so explicit values override environment variables and files correctly.

Harden Runtime Reloads

Validate candidate settings and synchronize updates before replacing active service configuration.

이 프롬프트를 사용해 보세요

Create Basic Configuration

Set up Viper for my Go service using a YAML file, MYAPP-prefixed environment variables, and sensible defaults.

Diagnose Environment Binding

Explain why MYAPP_DATABASE_HOST does not override database.host, then provide the correct Viper prefix, replacer, and AutomaticEnv setup.

Refactor Configuration Tests

Refactor my Viper tests to avoid shared global state. Use isolated instances and temporary environment values.

Design Safe Hot Reload

Design a production Viper reload flow that debounces events, decodes a candidate, validates it, and atomically updates synchronized application state.

모범 사례

Configure the environment prefix and key replacer before enabling automatic environment lookup.
Use explicit mapstructure tags and validate decoded configuration before application startup or reload.
Create a separate Viper instance for each test and protect shared runtime configuration with synchronization.

피하기

Do not rely on the global Viper instance across tests because state persists between cases.
Do not ignore every ReadInConfig error because malformed or unreadable files require attention.
Do not update shared configuration directly from a watch callback without validation and synchronization.