sindresorhus/pretty-bytes · Security & risks

Authoritative risk signals for sindresorhus/pretty-bytes — 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 · 3.8/10

Packaging—
Signed-Releases—
Pinned-Dependencies0/10
Maintained0/10
Token-Permissions0/10
CII-Best-Practices0/10
Fuzzing0/10
Branch-Protection0/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about sindresorhus/pretty-bytes

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.