Er Wegene sikker?
Wegene — Nerq Tillidsscore 42.5/100 (Karakter E). Baseret på analyse af 3 tillidsdimensioner vurderes det som har bemærkelsesværdige sikkerhedsproblemer. Sidst opdateret: 2026-04-02.
Vær forsigtig med Wegene. Wegene is a software tool with a Nerq Tillidsscore of 42.5/100 (E), based on 3 uafhængige datadimensioner. Det er under den anbefalede tærskel på 70. Vedligeholdelse: 0/100. Popularity: 0/100. Data hentet fra multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Sidst opdateret: 2026-04-02. Maskinlæsbare data (JSON).
Er Wegene sikker?
NEJ — BRUG MED FORSIGTIGHED — Wegene has a Nerq Tillidsscore of 42.5/100 (E). Har under gennemsnitlige tillidssignaler med betydelige huller i sikkerhed, vedligeholdelse eller dokumentation. Anbefales ikke til produktionsbrug uden grundig manuel gennemgang og yderligere sikkerhedsforanstaltninger.
Hvad er Wegenes tillidsscore?
Wegene has a Nerq Tillidsscore of 42.5/100, earning a E grade. This score is based on 3 independently measured dimensioner including sikkerhed, vedligeholdelse, and fællesskabsadoption.
Hvad er de vigtigste sikkerhedsresultater for Wegene?
Wegene's strongest signal is vedligeholdelse at 0/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.
Hvad er Wegene og hvem vedligeholder det?
| Udvikler | https://github.com/xraywu/mcp-wegene-assistant |
| Kategori | health |
| Stjerner | 4 |
| Kilde | https://github.com/xraywu/mcp-wegene-assistant |
Populære alternativer i health
What Is Wegene?
Wegene is a software tool in the health category: WeGene integrates with genetic testing APIs for personalized health and ancestry insights.. It has 4 GitHub stars. Nerq Tillidsscore: 42/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhed vulnerabilities, vedligeholdelse activity, license overholdelse, and fællesskabsadoption.
How Nerq Assesses Wegene's Safety
Nerq's Tillidsscore is calculated from 13+ independent signals aggregated into five dimensioner. Here is how Wegene performs in each:
- Vedligeholdelse (0/100): Wegene is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API dokumentation, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Baseret på GitHub stars, forks, download counts, and ecosystem integrations.
The overall Tillidsscore of 42.5/100 (E) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.
Who Should Use Wegene?
Wegene is designed for:
- Developers and teams working with health tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Wegene. The low trust score suggests potential risks in sikkerhed, vedligeholdelse, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Wegene's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Gennemgå repository sikkerhed policy, open issues, and recent commits for signs of active vedligeholdelse.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Wegene's dependency tree. - Anmeldelse permissions — Understand what access Wegene requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Wegene in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=WeGene - Gennemgå license — Confirm that Wegene's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
- Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses sikkerhed concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Wegene
When evaluating whether Wegene is safe, consider these category-specific risks:
Understand how Wegene processes, stores, and transmits your data. Gennemgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Wegene's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sikkerhed risk.
Regularly check for updates to Wegene. Sikkerhed patches and bug fixes are only effective if you're running the latest version.
If Wegene connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.
Verify that Wegene's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Wegene in violation of its license can expose your organization to legal liability.
Best Practices for Using Wegene Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Wegene while minimizing risk:
Periodically review how Wegene is used in your workflow. Check for unexpected behavior, permissions drift, and overholdelse with your sikkerhed policies.
Ensure Wegene and all its dependencies are running the latest stable versions to benefit from sikkerhed patches.
Grant Wegene only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Wegene's sikkerhed advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Wegene is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Wegene?
Even promising tools aren't right for every situation. Consider avoiding Wegene in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional overholdelse review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Wegene 42.5/100 meets your organization's risk tolerance. We recommend running a manual sikkerhed assessment alongside the automated Nerq score.
How Wegene Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among health tools, the average Tillidsscore is 62/100. Wegene's score of 42.5/100 is below the category average of 62/100.
This suggests that Wegene trails behind many comparable health tools. Organizations with strict sikkerhed requirements should evaluate whether higher-scoring alternatives better meet their needs.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderat in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.
Tillidsscore History
Nerq continuously monitors Wegene and recalculates its Tillidsscore as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or vedligeholdelse patterns change, Wegene's score is updated within 24 hours.
Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to sikkerhed and quality. Conversely, a downward trend may signal reduced vedligeholdelse, growing technical debt, or unresolved vulnerabilities. To track Wegene's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=WeGene&include=history
Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — sikkerhed, vedligeholdelse, dokumentation, overholdelse, and community — has evolved independently, providing granular visibility into which aspects of Wegene are strengthening or weakening over time.
Wegene vs Alternativer
I health-kategorien, Wegene scorer 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Wegene vs MedicalGPT — Tillidsscore: 62.6/100
- Wegene vs open-health — Tillidsscore: 62.6/100
- Wegene vs Awesome-AI4Med — Tillidsscore: 62.6/100
Vigtigste pointer
- Wegene has a Tillidsscore of 42.5/100 (E) and is not yet Nerq Verified.
- Wegene has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among health tools, Wegene scores below the category average of 62/100, suggesting room for improvement relative to peers.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Ofte stillede spørgsmål
Er Wegene sikker at bruge?
Hvad er tillidsscoren for Wegene?
Hvad er sikrere alternativer til Wegene?
How often is Wegene's safety score updated?
Kan jeg bruge Wegene i et reguleret miljø?
Disclaimer: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.