jesusfreke/smali · Security & risks

Authoritative risk signals for jesusfreke/smali — 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 →

OpenSSF Scorecard · 0.3/10

Token-Permissions—
Pinned-Dependencies—
Maintained0/10
License0/10
CI-Tests0/10
Dependency-Update-Tool0/10
Security-Policy0/10
SAST0/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about jesusfreke/smali

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.