Cmake Mcp est-il sûr ?
Cmake Mcp — Nerq Trust Score 62.9/100 (Note C). Score basé sur 5 independent trust signals.
Cmake Mcp est un software tool avec un Nerq Trust Score de 62.9/100 (C), basé sur 5 dimensions de données indépendantes. Sécurité: 0/100. Maintenance: 1/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: n/a. Données lisibles par machine (JSON).
Cmake Mcp est-il sûr ?
Détail du score de confiance — Cmake Mcp has a Nerq Trust Score of 62.9/100 (C). Measured across 5 independent trust signals.
Quel est le score de confiance de Cmake Mcp ?
Cmake Mcp a un Score de Confiance Nerq de 62.9/100, obtenant la note C. Ce score est basé sur 5 dimensions mesurées indépendamment.
Quels sont les résultats de sécurité clés pour Cmake Mcp ?
Le signal le plus fort de Cmake Mcp est conformité à 100/100. Aucune vulnérabilité connue n'a été détectée.
Qu'est-ce que Cmake Mcp et qui le maintient ?
| Auteur | ibuildrun |
| Catégorie | Devops |
| Source | https://github.com/ibuildrun/cmake-mcp |
| Protocols | mcp |
Conformité réglementaire
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Alternatives populaires dans devops
What Is Cmake Mcp?
Cmake Mcp is a DevOps tool: MCP server for CMake build automation and project management with structured error parsing.. Nerq Trust Score: 63/100 (C).
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 Cmake Mcp's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Cmake Mcp performs in each:
- Sécurité (0/100): Cmake Mcp's sécurité posture is poor. This score factors in known CVEs, dependency vulnerabilities, sécurité policy presence, and code signing practices.
- Maintenance (1/100): Cmake Mcp is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
- Compliance (100/100): Cmake Mcp is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Basé sur GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 62.9/100 (C) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.
Who Typically Evaluates Cmake Mcp?
Cmake Mcp is commonly evaluated by:
- Developers and teams working with devops tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Cmake Mcp's measured signals (sécurité 0/100, maintenance 1/100, documentation 1/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.
How to Verify Cmake Mcp's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Examiner le/la repository's sécurité policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Cmake Mcp's dependency tree. - Avis permissions — Understand what access Cmake Mcp requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Cmake Mcp 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=cmake-mcp - Examiner le/la license — Confirm that Cmake Mcp'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Cmake Mcp
When evaluating whether Cmake Mcp is safe, consider these category-specific risks:
Understand how Cmake Mcp processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Cmake Mcp's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.
Regularly check for updates to Cmake Mcp. Sécurité patches and bug fixes are only effective if you're running the latest version.
If Cmake Mcp 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 Cmake Mcp's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Cmake Mcp in violation of its license can expose your organization to legal liability.
Cmake Mcp and the EU AI Act
Cmake Mcp is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.
Nerq's conformité assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal conformité.
Best Practices for Using Cmake Mcp Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Cmake Mcp while minimizing risk:
Periodically review how Cmake Mcp is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.
Ensure Cmake Mcp and all its dependencies are running the latest stable versions to benefit from sécurité patches.
Grant Cmake Mcp only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Cmake Mcp's sécurité advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Cmake Mcp is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Cmake Mcp
Nerq's signals are one input. In the following situations, evaluate Cmake Mcp's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Cmake Mcp's measured trust score of 62.9/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Cmake Mcp is suitable for any particular use.
How Cmake Mcp Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Trust Score is 63/100. Cmake Mcp's score of 62.9/100 is near the category average of 63/100.
This places Cmake Mcp in line with the typical DevOps tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.
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 Cmake Mcp 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, Cmake Mcp'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 Cmake Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=cmake-mcp&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 Cmake Mcp are strengthening or weakening over time.
Cmake Mcp vs Alternatives
In the devops category, Cmake Mcp scores 62.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Cmake Mcp vs ansible — Trust Score: 74.9/100
- Cmake Mcp vs Flowise — Trust Score: 67.5/100
- Cmake Mcp vs learn-claude-code — Trust Score: 72.1/100
Points Essentiels
- Cmake Mcp has a measured Nerq Trust Score of 62.9/100 (C) — a composite of independent signals, not a suitability judgment.
- Among DevOps tools, Cmake Mcp scores near the category average of 63/100 (a positional measurement relative to peers).
- The individual signals — sécurité, maintenance, documentation, conformité, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Questions fréquentes
Cmake Mcp est-il sûr ?
Quel est le score de confiance de Cmake Mcp ?
Quelles sont les alternatives plus sûres à Cmake Mcp ?
À quelle fréquence le score de sécurité de Cmake Mcp est-il mis à jour ?
Puis-je utiliser Cmake Mcp dans un environnement réglementé ?
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.