Wegeneは安全ですか?

Wegene — Nerq Trust Score 42.5/100 (Eグレード). 3つの信頼次元の分析に基づき、顕著なセキュリティ上の懸念があると評価されています。 最終更新:2026-04-03。

Wegeneには注意が必要です。 Wegene is a software tool のNerq信頼スコアは 42.5/100 (E), based on 3 独立したデータ次元. It is below the recommended threshold of 70. メンテナンス: 0/100. Popularity: 0/100. データソース: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. 最終更新: 2026-04-03. 機械可読データ(JSON).

Wegeneは安全ですか?

NO — USE WITH CAUTION — Wegene のNerq信頼スコアは 42.5/100 (E). 平均以下の信頼シグナルで、重大なギャップがあります in セキュリティ, メンテナンス, or ドキュメント. Not recommended for production use without thorough manual review and additional セキュリティ measures.

セキュリティ分析 → プライバシーレポート →

Wegeneの信頼スコアは?

WegeneのNerq信頼スコアは42.5/100で、Eグレードです。このスコアはセキュリティ、メンテナンス、コミュニティ採用を含む3の独立した次元に基づいています。

メンテナンス
0
ドキュメント
0
人気度
0

Wegeneの主なセキュリティ調査結果は?

Wegeneの最も強いシグナルはメンテナンスで0/100です。 既知の脆弱性は検出されていません。 Nerq認証閾値70+にまだ達していません。

メンテナンス: 0/100 — メンテナンス活動が低い
Documentation: 0/100 — 限定的なドキュメント
Popularity: 0/100 — 4 スター( pulsemcp

Wegeneとは何で、誰が管理していますか?

作者https://github.com/xraywu/mcp-wegene-assistant
カテゴリhealth
Stars4
Sourcehttps://github.com/xraywu/mcp-wegene-assistant

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

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.

How Nerq Assesses Wegene's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 次元. Here is how Wegene performs in each:

The overall Trust Score 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 セキュリティ, メンテナンス, 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 — 確認してください repository セキュリティ policy, open issues, and recent commits for signs of active メンテナンス.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Wegene's dependency tree.
  3. レビュー 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. 確認してください 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 セキュリティ 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. 確認してください tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency セキュリティ

Check Wegene's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher セキュリティ risk.

Update frequency

Regularly check for updates to Wegene. セキュリティ 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 コンプライアンス

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 コンプライアンス with your セキュリティ policies.

Keep dependencies updated

Ensure Wegene and all its dependencies are running the latest stable versions to benefit from セキュリティ patches.

Follow least privilege

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

Monitor for セキュリティ advisories

Subscribe to Wegene's セキュリティ 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:

For each scenario, evaluate whether Wegeneの信頼スコア 42.5/100 meets your organization's risk tolerance. We recommend running a manual セキュリティ assessment alongside the automated Nerq score.

How Wegene 比較s to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among health tools, the average Trust Score 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 セキュリティ 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 中程度 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.

Trust Score History

Nerq continuously monitors Wegene and recalculates its Trust Score 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 メンテナンス 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 セキュリティ and quality. Conversely, a downward trend may signal reduced メンテナンス, 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 — セキュリティ, メンテナンス, ドキュメント, コンプライアンス, and community — has evolved independently, providing granular visibility into which aspects of Wegene are strengthening or weakening over time.

Wegene vs 代替品

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

重要なポイント

よくある質問

Is Wegene 安全に使用できます?
注意が必要です。 WeGene のNerq信頼スコアは 42.5/100 (E). 最も強いシグナル: メンテナンス (0/100). スコアの基準: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100).
Wegene's trust scoreとは?
WeGene: 42.5/100 (E). スコアの基準:: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=WeGene
Wegeneのより安全な代替品は?
In the health category, higher-rated alternatives include 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. データソース: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 42.5/100 (E), last 認証済み 2026-04-03. API: GET nerq.ai/v1/preflight?target=WeGene
Can I use Wegene in a regulated environment?
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の信頼スコアは、公開されている情報に基づく自動評価です。推奨や保証ではありません。必ずご自身でも確認してください。

We use cookies for analytics and caching. プライバシー Policy