Is Blake3 Safe?
Blake3 — Nerq Trust Score 58.7/100 (C grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-03-31.
Use Blake3 with some caution. Blake3 is a Python package with a Nerq Trust Score of 58.7/100 (C), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 80/100. Popularity: 80/100. Data sourced from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Machine-readable data (JSON).
Is Blake3 safe?
CAUTION — Blake3 has a Nerq Trust Score of 58.7/100 (C). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.
What is Blake3's trust score?
Blake3 has a Nerq Trust Score of 58.7/100, earning a C grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Blake3?
Blake3's strongest signal is security at 80/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.
What is Blake3 and who maintains it?
| Author | Jack O'Connor <[email protected]> |
| Category | pypi |
| Source | N/A |
Blake3 Across Platforms
Same developer/company in other registries:
Similar Pypi by Trust Score
Safety Guide: Blake3
What is Blake3?
Blake3 is a Python package — Python bindings for the Rust blake3 crate.
How to Verify Safety
Run pip audit or safety check. Review on PyPI for download stats.
You can also check the trust score via API: GET /v1/preflight?target=blake3
Key Safety Concerns for Python packages
When evaluating any Python package, watch for: dependency vulnerabilities, malicious uploads, maintenance status.
Trust Assessment
Blake3 has a Nerq Trust Score of 59/100 (C) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.
Key Takeaways
- Blake3 has a Trust Score of 59/100 (C).
- Review carefully before use — below trust threshold.
- Always verify independently using the Nerq API.
Detailed Score Analysis
| Dimension | Score |
|---|---|
| Security | 80/100 |
| Privacy | 80/100 |
| Reliability | 90/100 |
| Transparency | 85/100 |
| Maintenance | 60/100 |
Based on 5 dimensions. Data from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.
What data does Blake3 collect?
Blake3 is a Python package maintained by Jack O'Connor <[email protected]>. It receives approximately 2,082,600 weekly downloads. Licensed under CC0-1.0 OR Apache-2.0.
As a development package, Blake3 does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.
Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.
Full analysis: Blake3 Privacy Report · Privacy review
Is Blake3 secure?
Security score: 80/100. Blake3 has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.
Licensed under CC0-1.0 OR Apache-2.0, allowing code inspection. Open-source packages allow independent security review of the source code.
Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.
Full analysis: Blake3 Security Report
Blake3 Across Platforms
Same developer/company in other registries:
How we calculated this score
Blake3's trust score of 58.7/100 (C) is computed from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (80/100), privacy (80/100), reliability (90/100), transparency (85/100), maintenance (60/100). Each dimension is weighted equally to produce the composite trust score.
Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.
This page was last reviewed on March 31, 2026. Data version: 1.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Blake3 safe to use?
What is Blake3's trust score?
What are safer alternatives to Blake3?
Does Blake3 have known vulnerabilities?
How actively maintained is Blake3?
Popular in pypi
Browse Categories
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.