claritylab/lucida · Security & risks

Authoritative risk signals for claritylab/lucida — 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

5 direct

GHSA-p8p7-x288-28g6 · request (direct)Server-Side Request Forgery in RequestMODERATE

OpenSSF Scorecard · 2.1/10

Token-Permissions—
Dangerous-Workflow—
Packaging—
Signed-Releases—
Branch-Protection—
Maintained0/10
CII-Best-Practices0/10
Security-Policy0/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about claritylab/lucida

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.