nkanaev/yarr · Security & risks

Authoritative risk signals for nkanaev/yarr — 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

8 direct

OpenSSF Scorecard · 3.9/10

Code-Review0/10
CII-Best-Practices0/10
Token-Permissions0/10
SAST0/10
Security-Policy0/10
Fuzzing0/10
Signed-Releases0/10
Branch-Protection0/10

Ask AI about nkanaev/yarr

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.