Er 1111 sikker?

1111 — Nerq Trust Score 53.0/100 (Karakter C-). Baseret på analyse af 2 tillidsdimensioner vurderes det som har bemærkelsesværdige sikkerhedsproblemer. Sidst opdateret: 2026-04-05.

Brug 1111 med forsigtighed. 1111 er en NuGet package with a Nerq Trust Score of 53.0/100 (C-), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 90/100. Popularity: 45/100. Data sourced from nuget.org, GitHub, and NVD. Last updated: 2026-04-05. Maskinlæsbare data (JSON).

Er 1111 sikker?

CAUTION — 1111 has a Nerq Trust Score of 53.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.

Sikkerhedsanalyse → {name} privatlivsrapport →

Hvad er 1111s tillidsscore?

1111 har en Nerq Trust Score på 53.0/100 med karakteren C-. Denne score er baseret på 2 uafhængigt målte dimensioner, herunder sikkerhed, vedligeholdelse og community-adoption.

Sikkerhed
90
Popularitet
45

Hvad er de vigtigste sikkerhedsresultater for 1111?

1111s stærkeste signal er sikkerhed på 90/100. Ingen kendte sårbarheder er fundet. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 45/100 — community adoption

Hvad er 1111 og hvem vedligeholder det?

UdviklerUnknown
Kategorinuget
KildeN/A

Lignende Nuget efter tillidsscore

SFA.DAS.Http (62)BlazorInputFile (62)3Chum.IdentityServer4.AccessTokenValidation (62)Microsoft.KernelMemory.MemoryDb.Redis (62)Serilog.Exceptions.Grpc (62)
Se alle sikreste Nuget →

Compare

1111 vs SFA.DAS.Http1111 vs BlazorInputFile1111 vs 3Chum.IdentityServer4.AccessTokenValidation

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 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

Ofte stillede spørgsmål

Is 1111 safe to use?
Use with some caution. 1111 has a Nerq Trust Score of 53.0/100 (C-). Strongest signal: sikkerhed (90/100). Score based on security (90/100), popularity (45/100).
What is 1111's trust score?
1111: 53.0/100 (C-). Score based on: security (90/100), popularity (45/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=1111
What are safer alternatives to 1111?
In the nuget category, more NuGet packages are being analyzed — check back soon. 1111 scores 53.0/100.
Does 1111 have known vulnerabilities?
Nerq checks 1111 against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is 1111's publisher verified?
1111 has a trust score of 53.0/100 (C-). Below Nerq Verified threshold — conduct additional review.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.

Vi bruger cookies til analyse og caching. Privatliv