Thriving

↑ 61

fluxgate north-echo/fluxgate

CI/CD pipeline security scanner — 53 rules across GitHub Actions, GitLab CI, Azure Pipelines, Jenkins, Tekton, CircleCI

https://pkg.go.dev/github.com/north-echo/fluxgate/pkg/scanner ↗

HEALTH 97 / Healthy

// hidden gem cicddevsecopsgithub-actionsgitlab-cigogolangsecuritystatic-analysis

// readme

Fluxgate

CI/CD Pipeline Security Gate — static analysis for CI/CD pipeline configurations across 6 platforms.

Fluxgate scans workflow and pipeline files for dangerous security patterns, including the exact misconfiguration class that enabled the Trivy supply chain compromise in March 2026.

Quick Start

# Scan a local repository (auto-detects all 6 platforms)
fluxgate scan .

# Scan a remote repository
fluxgate remote aquasecurity/trivy

# Install
go install github.com/north-echo/fluxgate/cmd/fluxgate@latest

What It Detects

GitHub Actions (FG-xxx)

Rule	Severity	Description
FG-001	Critical	Pwn Request: pull_request_target with fork checkout
FG-002	High	Script Injection via expression interpolation
FG-003	Medium	Tag-based action pinning (mutable references)
FG-004	Medium	Overly broad workflow permissions
FG-005	Low	Secrets exposed in workflow logs
FG-006	Medium	Fork PR code execution via build hooks
FG-007	Medium	Token exposure in build steps
FG-008	Critical	OIDC…

↑ The Undervalued Score +

How much a project earns versus how much attention it actually gets. Above 50 means the work is outrunning its audience. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity — divided by a logarithmic reach factor.

score  = signal / reach

signal = 0.25·commit_velocity   // commits in last 90 days (cap 30)
       + 0.20·contributor_work  // unique authors × velocity (cap 100)
       + 0.20·issue_resolution  // closed ÷ total issues
       + 0.20·fork_ratio        // forks ÷ stars (proxy for real usage)
       + 0.10·release_cadence   // releases in 90 days (cap 3)
       + age_bonus              // +0 to +0.30 after 6 months
       + homepage_bonus         // +0.05 if homepage is set

reach  = log₁₀(stars + watchers + 10)█

♥ The 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.

health = 0.35·recency       // days since last commit (90d decay)
       + 0.25·cadence       // commit rhythm consistency
       + 0.20·issue_health  // closed ÷ total issues
       + 0.20·pr_health     // merged ÷ total PRs█

◷ Health bands +

The colour and label on every card come straight from the health score.

Healthy   80 – 100   active, responsive, regular releases
Stable    60 – 79    maintained, steady, no alarms
Quiet     40 – 59    slowing down — watch this one
At Risk    0 – 39    going dark · candidate for rescue█

// Tags — what each label means +

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

solo_builder      one person holds > 80% of commits (last 180d)
needs_contributors has open "help wanted" or "good first issue" labels
hidden_gem        < 100 stars · active in last 3 months · documented
legacy_hero       repo > 5 years old · committed this year
fork_magnet       forks/stars > 0.5 · used as template or dependency
release_machine   5+ releases in the last 90 days
under_pressure    > 10 open issues · ≤ 2 contributors · health ≥ 60
community_watch   watchers > stars · devs tracking before the public
community_hub     GitHub Discussions enabled · > 20 discussions
funded            maintainer has active funding channel█

★ Why rank against stars at all? +

Stars are an outcome, not effort. A project with 8 stars and daily commits is doing more interesting work than one coasting on 8k. We measure the building, then divide by the attention already received — so the genuinely undervalued rise to the top.

// stars   = lagging indicator
// commits = leading indicator
// we rank by the leading one█