emilk/egui · Security & risks
Authoritative risk signals for emilk/egui — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.
Dependency CVEs (deps.dev)
0
Critical
0 direct
0
High
0 direct
4
Moderate
50
Deps scanned
0 direct
- GHSA-64wv-8vwp-xgw2 · ashUse of Uninitialized Resource in ash.MODERATE
- RUSTSEC-2025-0141 · bincodeBincode is unmaintainedMODERATE
- GHSA-qj69-c89v-jwq2 · ashReading on uninitialized memory may cause UB ( `util::read_spv()` )MODERATE
- RUSTSEC-2021-0090 · ashReading on uninitialized memory may cause UB ( `util::read_spv()` )MODERATE
OpenSSF Scorecard · 4.5/10
- Packaging—
- Signed-Releases—
- CII-Best-Practices0/10
- Token-Permissions0/10
- Pinned-Dependencies0/10
- Fuzzing0/10
- Branch-Protection0/10
- Security-Policy0/10
Ask AI about emilk/egui
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 questionInformational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.