Is Brian Safe?
Brian — Nerq Trust Score 57.0/100 (C grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-05-13.
Use Brian with some caution. Brian is a Python package with a Nerq Trust Score of 57.0/100 (C), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 30/100. Data sourced from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-20. Machine-readable data (JSON).
Is Brian safe?
CAUTION — Brian has a Nerq Trust Score of 57.0/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 Brian's trust score?
Brian has a Nerq Trust Score of 57.0/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 Brian?
Brian's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.
What is Brian and who maintains it?
| Author | Romain Brette, Dan Goodman |
| Category | Python Packages |
| Source | N/A |
Similar Pypi by Trust Score
Safety Guide: Brian
What is Brian?
Brian is a Python package — A clock-driven simulator for spiking neural networks.
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=brian
Key Safety Concerns for Python package
When evaluating any Python package, watch for: dependency vulnerabilities, malicious uploads, maintenance status.
Trust Assessment
Brian has a Nerq Trust Score of 57/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
- Brian has a Trust Score of 57/100 (C).
- Review carefully before use — below trust threshold.
- Always verify independently using the Nerq API.
Detailed Score Analysis
| Dimension | Score |
|---|---|
| Security | 90/100 |
| Maintenance | 67/100 |
| Popularity | 30/100 |
| Quality | 40/100 |
| Community | 35/100 |
Based on 5 dimensions. Data from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.
What data does Brian collect?
Privacy assessment for Brian is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.
Is Brian secure?
Security score: 90/100. Brian has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.
License information not available. 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: Brian Security Report
How we calculated this score
Brian's trust score of 57.0/100 (C) is computed from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), maintenance (67/100), popularity (30/100), quality (40/100), community (35/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 May 13, 2026. Data version: 0.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Brian Safe?
What is Brian's trust score?
What are safer alternatives to Brian?
Does Brian have known vulnerabilities?
Is Brian actively maintained?
Popular in Python Packages
Browse Categories
See Also
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.