textualize/rich · Security & risks

Authoritative risk signals for textualize/rich — 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 · 7.2/10

Branch-Protection0/10
Pinned-Dependencies2/10
Code-Review2/10
Maintained8/10
License10/10
CI-Tests10/10
Dependency-Update-Tool10/10
Security-Policy10/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about textualize/rich

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.