golang-security
Review Go Code for Security Risks
Go services can expose sensitive data through unsafe input handling, weak authentication, and insecure configuration. This skill guides structured reviews, threat modeling, and mitigation planning.
安裝前請停止並請求確認。
請審查安裝計畫,並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "golang-security" from https://skillstore.io/skills/samber-golang-security.md and its manifest at https://skillstore.io/api/skills/samber-golang-security/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「golang-security」。 Review a handler that inserts a request name directly into a SQL query.
預期結果:
- Finding: SQL injection through a request-controlled name.
- Impact: An attacker could change query logic and access unauthorized records.
- Recommendation: Pass the name as a query parameter rather than concatenating it.
- Verification: Add a regression test with SQL metacharacters and confirm the input remains data.
正在使用「golang-security」。 Threat-model a webhook receiver that stores events and publishes queue messages.
預期結果:
- Spoofing and tampering: Verify webhook signatures and enforce a replay policy.
- Denial of service: Limit request sizes, processing time, and submission rates.
- Information disclosure: Protect transport connections and exclude secrets from logs.
- Repudiation: Record event identifiers and processing outcomes in structured audit logs.
安全審計
高風險All 152 static alerts are false positives involving defensive examples, evaluation fixtures, documentation formatting, or unrelated keyword combinations. No evidence found of credential exfiltration or prompt injection targeting this audit. Two semantic findings identify unsafe XSS guidance and incomplete SSRF defenses that could introduce vulnerabilities into generated applications.
已確認的安全問題 (2)
風險因素
⚙️ 外部命令 (38)
🌐 網路存取 (18)
📁 檔案系統存取 (9)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/samber-golang-security/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/samber-golang-security?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/samber-golang-security?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-security/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/samber-golang-security.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-security security audit report (audit version 1) [Author version 1.2.2]. Skillstore. https://skillstore.io/skills/samber-golang-security/audits/1BibTeX 引用
@techreport{samber-samber-golang-security-2026,
author = {samber},
title = {golang-security security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-security/audits/1},
note = {Author version 1.2.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-security security audit report (audit version 1)"
version: "1.2.2"
type: report
authors:
- name: "samber"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/samber-golang-security/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-security:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Review a Go Pull Request
Trace changed handlers and adjacent data flows to identify exploitable input, authorization, and configuration risks.
Audit a Service
Organize a codebase review by vulnerability domain and prioritize findings with evidence and remediation recommendations.
Model System Threats
Map trust boundaries across APIs, databases, queues, and external integrations before choosing security controls.
試試這些提示
Review [handler] for security risks. Explain untrusted inputs, existing protections, and recommended fixes. Do not modify files.
Review [pull request or diff] for security issues. Trace relevant call sites and validation. Report evidence, exploitability, severity, and focused remediation.
Design secure file serving for [service] using Go [version]. Address traversal, symlinks, permissions, resource limits, and regression tests. Explain remaining assumptions.
Audit [repository] across injection, cryptography, web security, authorization, and concurrency. Apply STRIDE and DREAD. Separate exploitable findings from hardening recommendations. Propose verification tests.
最佳實務
- Provide relevant code, deployment context, Go version, and trust boundaries before requesting a review.
- Validate recommendations against current library behavior and distinguish demonstrated exploits from optional hardening.
- Verify each mitigation with focused regression tests and appropriate static, race, or fuzz testing.
避免
- Treating instructional snippets or generated fixes as production-ready without independent review.
- Sharing live credentials, private keys, or unnecessary personal data in review prompts.
- Equating keyword matches or severity scores with proven exploitability.
常見問題
Which assistants can use this skill?
Does this skill automatically scan my code?
What Go versions do the examples target?
Are all recommendations safe to copy directly?
Can it help prioritize vulnerabilities?
Does it replace dependency management or CI configuration?
開發者詳細資訊
作者
samber授權
MIT
作者版本
v1.2.2
Skillstore 修訂
r1
引用
61e08cf7198fc8690b316eaf44afa6467c180924
維護新鮮度
2026/10/15
使用量
0 次下載 · 0 次瀏覽
檔案結構