独立运营 · 不出售排名位置  · 我们怎么评估工具 →
Anclum 提交收录
D

draugr-dev/draugr

本站为独立目录,非该工具官网;下方信息取自其公开仓库。

Describe your app in one file, and Draugr hands back the findings in the order to fix them. (原文为英文)

30 ★ 本站实测 · 核对 2026-11-19

装之前:没有可直接复制的命令 · 许可证 Apache-2.0

第一步:这条暂时没有可执行的下一步,可先看原仓库 https://github.com/draugr-dev/draugr

★ 30·更新 2026-11-19
在 GitHub 查看 ↗直链 · 无中转页

我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →

★ 数取值
30 ★ · draugr-dev/draugr · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
来源明细
收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
评分构成
综合分 300 · 30 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 draugr-dev/draugr;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
README 原文(英文,未翻译) · 在 GitHub 读完整 README →

# Draugr

以下摘录自该仓库的 README(片段)

> Know which security findings to fix first, across the scanners you already run. SAST, SCA, secrets, IaC and containers, every finding ranked by exposure, criticality, exploitability and, for Go, reachability.
Describe your app in one file, and Draugr hands back the findings in the order to fix them.
Every application carries problems nobody put there on purpose: a library that turned out to have a
hole in it, a password committed by accident, a server setting that leaves a door open. Draugr finds
them, works out which ones actually matter for your app, and answers the question you are really
asking before a release, is this safe to ship?
It runs the established open-source scanners for you, Trivy, Semgrep, Gitleaks and others, so there
is nothing to choose between, wire up, or read five of. You describe what you built, once, in one
file: where the repositories are, what images it builds, what it exposes, what infrastructure it
runs on. Draugr picks the checks that apply, runs the right tool for each, and produces evidence you
can hand to somebody else. Bring the scanners you already pay for, or use the open-source defaults.
Findings are ranked, not listed. A scanner's "critical" describes a flaw in the abstract,
how bad it could be at its worst, anywhere. The same flaw is act-now in the service strangers can
reach and backlog in the internal tool three people use, and no scanner can tell those apart because
the difference is in the file you wrote, not in the code. And draugr diff
gates a pull request on new findings only, so inheriting two hundred existing ones does not
block every change.
Quickstart · See it in action ·
What it checks · In your pipeline ·
Documentation · What Draugr doesn't promise ·
Security
## See it in action
Priority (P1–P4) is not severity. Severity says how bad a flaw is at its worst, anywhere.
Priority weighs that against how exposed and how important the part of your app it sits in is, which
no scanner can work out, because it is not in the code.
draugr-dev/draugr-demo is a deliberately
vulnerable app wired to Draugr: every control lights up, findings land in the repo's
Security → Code scanning tab, and its example pull requests show the new-vs-fixed diff.
## Quickstart
bash
curl -fsSL https://draugr.dev/install.sh | sh
Installs to ~/.local/bin, no sudo, and installs nothing if the archive fails
verification. The script is readable in the
repo; a download by hand, the GitHub CLI and go install are in the install
guide.
bash
draugr tools install # fetch the scanners a scan here runs, pinned and verified
draugr scan . # scan this repository, no descriptor needed
tools install reads the tree as draugr init does, or the descriptor beside it, so a small service
gets the few scanners it runs rather than every one Draugr can provision. --all when you are
preparing a machine for several projects.
Then describe what you actually ship, with draugr init writing a first draft:
yaml
project: my-app
release:
version: "1.0"
config:
controls:
images:
enabled: true
components:
name: web
images:
image: alpine:3.19
bash
draugr scan draugr.saga.yaml # console summary; exits non-zero on fail
draugr scan draugr.saga.yaml -o out/ # also writes report.json + results.sarif
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/zh/s/draugr-dev-draugr/)
来源
awesome · https://github.com/draugr-dev/draugr
按领域浏览
MCP 服务
Traction
30 ★
收录来源
3 个独立来源
收录于
今天

更多 MCP 服务器

全部 6,555 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引