Thriving Thriving Go GO
↑ 43
draugr draugr-dev/draugr

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.

https://draugr.dev β†—
HEALTH 97 / Healthy
// solo builder// hidden gem appsecclicode-scanningcontainer-securitydastdevsecopsgithub-actiongolangiac-securitysarif

// momentum

tracking since W47

// why it's here

  • Active: last commit today
  • Built almost entirely by one person
  • Health 97/100 with only 30 stars

// how to help

// readme

Draugr

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?

Read the full README on GitHub β†—

Health score

Is the project alive and maintained right now? A 0–100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.

How it's calculated

Undervalued score

Activity relative to attention (stars + watchers). Above 50 means a lot of activity for a project its size. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity β€” divided by a logarithmic reach factor.

How it's calculated

Tags

Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.

How it's calculated