Is Wegene veilig?

Wegene — Nerq Vertrouwensscore 42.5/100 (E-beoordeling). Op basis van analyse van 3 vertrouwensdimensies wordt het beschouwd als heeft opmerkelijke beveiligingszorgen. Laatst bijgewerkt: 2026-04-03.

Wees voorzichtig met Wegene. Wegene is a software tool met een Nerq Vertrouwensscore van 42.5/100 (E), based on 3 onafhankelijke gegevensdimensies. Het ligt onder de aanbevolen drempel van 70. Onderhoud: 0/100. Popularity: 0/100. Gegevens afkomstig van multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Laatst bijgewerkt: 2026-04-03. Machineleesbare gegevens (JSON).

Is Wegene veilig?

NEE — GEBRUIK MET VOORZICHTIGHEID — Wegene heeft een Nerq Vertrouwensscore van 42.5/100 (E). Het heeft benedengemiddelde vertrouwenssignalen met aanzienlijke lacunes in beveiliging, onderhoud of documentatie. Niet aanbevolen voor productiegebruik zonder grondige handmatige controle en aanvullende beveiligingsmaatregelen.

Beveiligingsanalyse → {name} Privacyrapport →

Wat is de vertrouwensscore van Wegene?

Wegene heeft een Nerq Vertrouwensscore van 42.5/100, earning a E grade. This score is based on 3 independently measured dimensies including beveiliging, onderhoud, and gemeenschapsacceptatie.

Onderhoud
0
Documentatie
0
Populariteit
0

Wat zijn de belangrijkste beveiligingsbevindingen voor Wegene?

Wegene's strongest signal is onderhoud at 0/100. No bekende kwetsbaarheden have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Onderhoud: 0/100 — lage onderhoudsactiviteit
Documentation: 0/100 — beperkte documentatie
Popularity: 0/100 — 4 sterren op pulsemcp

Wat is Wegene en wie onderhoudt het?

Ontwikkelaarhttps://github.com/xraywu/mcp-wegene-assistant
Categoriehealth
Sterren4
Bronhttps://github.com/xraywu/mcp-wegene-assistant

Populaire alternatieven in health

shibing624/MedicalGPT
62.6/100 · C
github
OpenHealthForAll/open-health
62.6/100 · C
github
FreedomIntelligence/Awesome-AI4Med
62.6/100 · C
github
scutcyr/BianQue
59.0/100 · D
github
huifer/WellAlly-health
61.4/100 · C
github

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 Vertrouwensscore: 42/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.

How Nerq Assesses Wegene's Safety

Nerq's Vertrouwensscore is calculated from 13+ independent signals aggregated into five dimensies. Here is how Wegene performs in each:

The overall Vertrouwensscore 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:

Risk guidance: We recommend caution with Wegene. The low trust score suggests potential risks in beveiliging, onderhoud, 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:

  1. Check the source code — Bekijk de repository beveiliging policy, open issues, and recent commits for signs of active onderhoud.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for bekende kwetsbaarheden in Wegene's dependency tree.
  3. Beoordeling permissions — Understand what access Wegene requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Wegene in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=WeGene
  6. Bekijk de 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.
  7. 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 beveiliging 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:

Data handling

Understand how Wegene processes, stores, and transmits your data. Bekijk de tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency beveiliging

Check Wegene's dependency tree for bekende kwetsbaarheden. Tools with outdated or unmaintained dependencies pose a higher beveiliging risk.

Update frequency

Regularly check for updates to Wegene. Beveiliging patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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.

License and IP naleving

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:

Conduct regular audits

Periodically review how Wegene is used in your workflow. Check for unexpected behavior, permissions drift, and naleving with your beveiliging policies.

Keep dependencies updated

Ensure Wegene and all its dependencies are running the latest stable versions to benefit from beveiliging patches.

Follow least privilege

Grant Wegene only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for beveiliging advisories

Subscribe to Wegene's beveiliging advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

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:

de vertrouwensscore van

For each scenario, evaluate whether Wegene is 42.5/100 meets your organization's risk tolerance. We recommend running a manual beveiliging 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 Vertrouwensscore 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 beveiliging 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 matig 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.

Vertrouwensscore History

Nerq continuously monitors Wegene and recalculates its Vertrouwensscore 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 onderhoud 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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, 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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Wegene are strengthening or weakening over time.

Wegene vs Alternatieven

In the health category, Wegene scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Belangrijkste conclusies

Veelgestelde vragen

Is Wegene veilig om te gebruiken?
Wees voorzichtig. WeGene heeft een Nerq Vertrouwensscore van 42.5/100 (E). Sterkste signaal: onderhoud (0/100). Score gebaseerd op onderhoud (0/100), populariteit (0/100), documentatie (0/100).
Wat is Wegene's trust score?
WeGene: 42.5/100 (E). Score gebaseerd op: onderhoud (0/100), populariteit (0/100), documentatie (0/100). Scores worden bijgewerkt naarmate nieuwe gegevens beschikbaar komen. API: GET nerq.ai/v1/preflight?target=WeGene
Wat zijn veiligere alternatieven voor Wegene?
In the health category, hoger beoordeelde alternatieven zijn onder meer shibing624/MedicalGPT (63/100), OpenHealthForAll/open-health (63/100), FreedomIntelligence/Awesome-AI4Med (63/100). WeGene scores 42.5/100.
How often is Wegene's safety score updated?
Nerq continuously monitors Wegene and updates its trust score as new data becomes available. Gegevens afkomstig van multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 42.5/100 (E), last geverifieerd 2026-04-03. API: GET nerq.ai/v1/preflight?target=WeGene
Kan ik Wegene gebruiken in een gereguleerde omgeving?
Wegene has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq-vertrouwensscores zijn geautomatiseerde beoordelingen op basis van openbaar beschikbare signalen. Ze vormen geen aanbeveling of garantie. Voer altijd uw eigen verificatie uit.

We use cookies for analytics and caching. Privacy Policy