thomaspoignant/go-feature-flag · Security & risks

Authoritative risk signals for thomaspoignant/go-feature-flag — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.

Architecture Security & risks Dependencies License Maintenance Alternatives Vs Full analysis

Dependency CVEs (deps.dev)

Critical

0 direct

High

0 direct

Moderate

Deps scanned

25 direct

OpenSSF Scorecard · 7.0/10

Fuzzing0/10
Vulnerabilities0/10
Token-Permissions1/10
Branch-Protection3/10
CII-Best-Practices5/10
Signed-Releases6/10
Code-Review8/10
Pinned-Dependencies8/10

Ask AI about thomaspoignant/go-feature-flag

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.