Is 1111 Safe?
Exercise caution with 1111. 1111 is a NuGet package with a Nerq Trust Score of 46.2/100 (D), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 90/100. Popularity: 0/100. Data sourced from nuget.org, GitHub, and NVD. Last updated: 2026-03-27. Machine-readable data (JSON).
Is 1111 safe?
NO — USE WITH CAUTION — 1111 has a Nerq Trust Score of 46.2/100 (D). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.
Trust Score Breakdown
Key Findings
Details
| Author | Unknown |
| Category | nuget |
| Source | N/A |
Safety Guide: 1111
What is 1111?
1111 is a NuGet package.
How to Verify Safety
Run dotnet list package --vulnerable. Check publisher on nuget.org.
You can also check the trust score via API: GET /v1/preflight?target=1111
Key Safety Concerns for NuGet packages
When evaluating any NuGet package, watch for: dependency vulnerabilities, publisher verification.
Trust Assessment
1111 has a Nerq Trust Score of 46/100 (D) 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
- 1111 has a Trust Score of 46/100 (D).
- Review carefully before use — below trust threshold.
- Always verify independently using the Nerq API.
Frequently Asked Questions
Is 1111 safe to use?
What is 1111's trust score?
What are safer alternatives to 1111?
Does 1111 have known vulnerabilities?
Is 1111's publisher verified?
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.