Is Avici Safe?
Avici — Nerq Trust Score 52.5/100 (C- grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-04-23.
Use Avici with some caution. Avici is a Python package with a Nerq Trust Score of 52.5/100 (C-), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 15/100. Data sourced from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-20. Machine-readable data (JSON).
Is Avici safe?
CAUTION — Avici has a Nerq Trust Score of 52.5/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 Avici's trust score?
Avici has a Nerq Trust Score of 52.5/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 Avici?
Avici'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 Avici and who maintains it?
| Author | Lars Lorch |
| Category | Python Packages |
| Source | N/A |
Similar Pypi by Trust Score
Safety Guide: Avici
What is Avici?
Avici is a Python package — Amortized Inference for Causal Structure Learning.
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=avici
Key Safety Concerns for Python package
When evaluating any Python package, watch for: dependency vulnerabilities, malicious uploads, maintenance status.
Trust Assessment
Avici has a Nerq Trust Score of 52/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
- Avici has a Trust Score of 52/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 | 58/100 |
| Popularity | 15/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 Avici collect?
Privacy assessment for Avici is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.
Is Avici secure?
Security score: 90/100. Avici 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: Avici Security Report
How we calculated this score
Avici's trust score of 52.5/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 (58/100), popularity (15/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 April 23, 2026. Data version: 0.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Avici Safe?
What is Avici's trust score?
What are safer alternatives to Avici?
Does Avici have known vulnerabilities?
Is Avici 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.