Is Fluentsharp.Bcl Safe?
Fluentsharp.Bcl — Nerq Trust Score 53.2/100 (C- grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-05-31.
Use Fluentsharp.Bcl with some caution. Fluentsharp.Bcl is a NuGet package with a Nerq Trust Score of 53.2/100 (C-), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 0/100. Data sourced from nuget.org, GitHub, and NVD. Last updated: 2026-03-20. Machine-readable data (JSON).
Is Fluentsharp.Bcl safe?
CAUTION — Fluentsharp.Bcl has a Nerq Trust Score of 53.2/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 Fluentsharp.Bcl's trust score?
Fluentsharp.Bcl has a Nerq Trust Score of 53.2/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 Fluentsharp.Bcl?
Fluentsharp.Bcl'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 Fluentsharp.Bcl and who maintains it?
| Author | O2 Platform |
| Category | NuGet Packages |
| Source | N/A |
Similar Nuget by Trust Score
Compare
Safety Guide: Fluentsharp.Bcl
What is Fluentsharp.Bcl?
Fluentsharp.Bcl is a NuGet package — FluentSharp is an API that dramatically simplifies the use of .NET Framework APIs. This is the Fluent# BCL which provides support for System.Forms and Web.
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=FluentSharp.BCL
Key Safety Concerns for NuGet package
When evaluating any NuGet package, watch for: dependency vulnerabilities, publisher verification.
Trust Assessment
Fluentsharp.Bcl has a Nerq Trust Score of 53/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
- Fluentsharp.Bcl has a Trust Score of 53/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 | 50/100 |
| Popularity | 0/100 |
| Quality | 65/100 |
| Community | 35/100 |
Based on 5 dimensions. Data from nuget.org, GitHub, and NVD.
What data does Fluentsharp.Bcl collect?
Privacy assessment for Fluentsharp.Bcl is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.
Is Fluentsharp.Bcl secure?
Security score: 90/100. This meets the recommended security threshold for production use.
Nerq monitors this entity against NVD, OSV.dev, and registry-specific vulnerability databases for ongoing security assessment.
Full analysis: Fluentsharp.Bcl Security Report
How we calculated this score
Fluentsharp.Bcl's trust score of 53.2/100 (C-) is computed from nuget.org, GitHub, and NVD. The score reflects 5 independent dimensions: security (90/100), maintenance (50/100), popularity (0/100), quality (65/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 31, 2026. Data version: 0.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Fluentsharp.Bcl Safe?
What is Fluentsharp.Bcl's trust score?
What are safer alternatives to Fluentsharp.Bcl?
Does Fluentsharp.Bcl have known vulnerabilities?
Is Fluentsharp.Bcl's publisher verified?
Popular in NuGet Packages
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.