Codegeex2 est-il sûr ?

Codegeex2 — Nerq Trust Score 70.6/100 (Note B). Sur la base de l'analyse de 5 dimensions de confiance, il est généralement sûr mais avec quelques préoccupations. Dernière mise à jour : 2026-04-07.

Oui, Codegeex2 est sûr à utiliser. Codegeex2 est un software tool avec un Nerq Trust Score de 70.6/100 (B), basé sur 5 dimensions de données indépendantes. Recommandé pour utilisation. Sécurité: 0/100. Maintenance: 0/100. Popularité: 0/100. Données de plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard. Dernière mise à jour: 2026-04-07. Données lisibles par machine (JSON).

Codegeex2 est-il sûr ?

YES — Codegeex2 has a Nerq Trust Score of 70.6/100 (B). Il dépasse le seuil de confiance Nerq avec des signaux forts en sécurité, maintenance et adoption communautaire. Recommandé pour utilisation — consultez le rapport complet ci-dessous pour des considérations spécifiques.

Analyse de Sécurité → Rapport de confidentialité de Codegeex2 →

Quel est le score de confiance de Codegeex2 ?

Codegeex2 a un Score de Confiance Nerq de 70.6/100, obtenant la note B. Ce score est basé sur 5 dimensions mesurées indépendamment.

Sécurité
0
Conformité
100
Maintenance
0
Documentation
0
Popularité
0

Quels sont les résultats de sécurité clés pour Codegeex2 ?

Le signal le plus fort de Codegeex2 est conformité à 100/100. Aucune vulnérabilité connue n'a été détectée. Atteint le seuil vérifié Nerq de 70+.

Score de sécurité: 0/100 (faible)
Maintenance: 0/100 — faible activité de maintenance
Conformité: 100/100 — covers 52 of 52 jurisdictions
Documentation: 0/100 — documentation limitée
Popularité: 0/100 — 7,605 étoiles sur github

Qu'est-ce que Codegeex2 et qui le maintient ?

AuteurUnknown
CatégorieAi Tool
Étoiles7,605
Sourcehttps://github.com/zai-org/CodeGeeX2

Conformité réglementaire

EU AI Act Risk ClassNot assessed
Compliance Score100/100
JurisdictionsAssessed across 52 jurisdictions

Alternatives populaires dans AI tool

openclaw/openclaw
84.3/100 · A
github
AUTOMATIC1111/stable-diffusion-webui
69.3/100 · C
github
f/prompts.chat
69.3/100 · C
github
microsoft/generative-ai-for-beginners
71.8/100 · B
github
Comfy-Org/ComfyUI
71.8/100 · B
github

What Is Codegeex2?

Codegeex2 is a software tool in the AI tool category: CodeGeeX2: A More Powerful Multilingual Code Generation Model. It has 7,605 GitHub stars. Nerq Trust Score: 71/100 (B).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sécurité vulnerabilities, maintenance activity, license conformité, and adoption par la communauté.

How Nerq Assesses Codegeex2's Safety

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

The overall Trust Score of 70.6/100 (B) reflects the weighted combination of these signals. This exceeds the Nerq Verified threshold of 70, indicating the tool meets our standards for production use.

Who Should Use Codegeex2?

Codegeex2 is designed for:

Risk guidance: Codegeex2 meets the minimum threshold for production use, but we recommend monitoring for sécurité advisories and keeping dependencies up to date. Consider implementing additional guardrails for sensitive workloads.

How to Verify Codegeex2's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — Examiner le/la repository's sécurité policy, open issues, and recent commits for signs of active maintenance.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Codegeex2's dependency tree.
  3. Avis permissions — Understand what access Codegeex2 requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Codegeex2 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=zai-org/CodeGeeX2
  6. Examiner le/la license — Confirm that Codegeex2'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Codegeex2

When evaluating whether Codegeex2 is safe, consider these category-specific risks:

Data handling

Understand how Codegeex2 processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sécurité

Check Codegeex2's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.

Update frequency

Regularly check for updates to Codegeex2. Sécurité patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Codegeex2 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 conformité

Verify that Codegeex2's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Codegeex2 in violation of its license can expose your organization to legal liability.

Best Practices for Using Codegeex2 Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Codegeex2 while minimizing risk:

Conduct regular audits

Periodically review how Codegeex2 is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.

Keep dependencies updated

Ensure Codegeex2 and all its dependencies are running the latest stable versions to benefit from sécurité patches.

Follow least privilege

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

Monitor for sécurité advisories

Subscribe to Codegeex2's sécurité 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 Codegeex2 is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Codegeex2?

Even well-trusted tools aren't right for every situation. Consider avoiding Codegeex2 in these scenarios:

For each scenario, evaluate whether Codegeex2's trust score of 70.6/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.

How Codegeex2 Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among AI tool tools, the average Trust Score is 62/100. Codegeex2's score of 70.6/100 is above the category average of 62/100.

This positions Codegeex2 favorably among AI tool tools. While it outperforms the average, there is still room for improvement in certain trust dimensions.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks modéré 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 Codegeex2 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 maintenance patterns change, Codegeex2'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 sécurité and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Codegeex2's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=zai-org/CodeGeeX2&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 — sécurité, maintenance, documentation, conformité, and community — has evolved independently, providing granular visibility into which aspects of Codegeex2 are strengthening or weakening over time.

Codegeex2 vs Alternatives

In the AI tool category, Codegeex2 scores 70.6/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Points Essentiels

Questions fréquentes

Codegeex2 est-il sûr ?
Oui, il est sûr à utiliser. zai-org/CodeGeeX2 avec un Nerq Trust Score de 70.6/100 (B). Signal le plus fort : conformité (100/100). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100).
Quel est le score de confiance de Codegeex2 ?
zai-org/CodeGeeX2: 70.6/100 (B). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100). Compliance: 100/100. Les scores sont mis à jour lorsque de nouvelles données sont disponibles. API: GET nerq.ai/v1/preflight?target=zai-org/CodeGeeX2
Quelles sont les alternatives plus sûres à Codegeex2 ?
Dans la catégorie Ai Tool, higher-rated alternatives include openclaw/openclaw (84/100), AUTOMATIC1111/stable-diffusion-webui (69/100), f/prompts.chat (69/100). zai-org/CodeGeeX2 scores 70.6/100.
À quelle fréquence le score de sécurité de Codegeex2 est-il mis à jour ?
Nerq continuously monitors Codegeex2 and updates its trust score as new data becomes available. Current: 70.6/100 (B), last vérifié 2026-04-07. API: GET nerq.ai/v1/preflight?target=zai-org/CodeGeeX2
Puis-je utiliser Codegeex2 dans un environnement réglementé ?
Codegeex2 atteint le seuil de vérification Nerq (70+). Sûr pour la production.
API: /v1/preflight Trust Badge API Docs

Voir aussi

Disclaimer: Les scores de confiance Nerq sont des évaluations automatisées basées sur des signaux publiquement disponibles. Ce ne sont pas des recommandations ou des garanties. Effectuez toujours votre propre vérification.

Nous utilisons des cookies pour l'analyse et le cache. Confidentialité