go-gorm/gorm · Security & risks

Authoritative risk signals for go-gorm/gorm — 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

3 direct

OpenSSF Scorecard · 4.3/10

Packaging—
Signed-Releases—
Branch-Protection—
CII-Best-Practices0/10
Token-Permissions0/10
Pinned-Dependencies0/10
Fuzzing0/10
Security-Policy0/10

Ask AI about go-gorm/gorm

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.