Cmake Mcp có an toàn không?
Cmake Mcp — Nerq Trust Score 62.9/100 (Hạng C). Điểm dựa tr��n 5 independent trust signals.
Cmake Mcp là một software tool với Điểm tin cậy Nerq 62.9/100 (C), dựa trên 5 chiều dữ liệu độc lập. Bảo mật: 0/100. Bảo trì: 1/100. Độ phổ biến: 0/100. Dữ liệu từ nhiều nguồn công khai bao gồm registry gói, GitHub, NVD, OSV.dev và OpenSSF Scorecard. Cập nhật lần cuối: n/a. Dữ liệu máy đọc được (JSON).
Cmake Mcp có an toàn không?
Chi tiết điểm tin cậy — Cmake Mcp has a Nerq Trust Score of 62.9/100 (C). Measured across 5 independent trust signals.
Điểm tin cậy của Cmake Mcp là bao nhiêu?
Cmake Mcp có Điểm tin cậy Nerq là 62.9/100 với xếp hạng C. Điểm này dựa trên 5 chiều dữ liệu được đo lường độc lập bao gồm bảo mật, bảo trì và sự chấp nhận của cộng đồng.
Các phát hiện bảo mật chính của Cmake Mcp là gì?
Tín hiệu mạnh nhất của Cmake Mcp là tuân thủ ở mức 100/100. Không phát hiện lỗ hổng đã biết.
Cmake Mcp là gì và ai duy trì nó?
| Nhà phát triển | ibuildrun |
| Danh mục | Devops |
| Nguồn | https://github.com/ibuildrun/cmake-mcp |
| Protocols | mcp |
Tuân thủ quy định
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Quyền Tài Pháns | Assessed across 52 quyền tài pháns |
Lựa chọn phổ biến trong 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 bảo mật vulnerabilities, bảo trì activity, license tuân thủ, and sự chấp nhận của cộng đồng.
How Nerq Assesses Cmake Mcp's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five tiêu chí. Here is how Cmake Mcp performs in each:
- Bảo mật (0/100): Cmake Mcp's bảo mật posture is poor. This score factors in known CVEs, dependency vulnerabilities, bảo mật policy presence, and code signing practices.
- Bảo trì (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 tài liệu, usage examples, and contribution guidelines.
- Compliance (100/100): Cmake Mcp is broadly compliant. Assessed against regulations in 52 quyền tài pháns including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Dựa trên sao GitHub, 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 (bảo mật 0/100, bảo trì 1/100, tài liệu 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 — Xem xét repository's bảo mật policy, open issues, and recent commits for signs of active bảo trì.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Cmake Mcp's dependency tree. - Đánh giá 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 - Xem xét 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 bảo mật 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. Xem xét 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 bảo mật risk.
Regularly check for updates to Cmake Mcp. Bảo mật 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 tuân thủ assessment covers 52 quyền tài pháns worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal tuân thủ.
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 tuân thủ with your bảo mật policies.
Ensure Cmake Mcp and all its dependencies are running the latest stable versions to benefit from bảo mật patches.
Grant Cmake Mcp only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Cmake Mcp's bảo mật 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 Độc lập 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 trung bình 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 bảo trì 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 bảo mật and quality. Conversely, a downward trend may signal reduced bảo trì, 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 — bảo mật, bảo trì, tài liệu, tuân thủ, and community — has evolved independently, providing granular visibility into which aspects of Cmake Mcp are strengthening or weakening over time.
Cmake Mcp vs Lựa chọn thay thế
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
Điểm chính
- 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 — bảo mật, bảo trì, tài liệu, tuân thủ, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Câu hỏi thường gặp
Cmake Mcp có an toàn không?
Điểm tin cậy của Cmake Mcp là bao nhiêu?
Các lựa chọn an toàn hơn Cmake Mcp là gì?
Điểm an toàn của Cmake Mcp được cập nhật bao lâu một lần?
Tôi có thể sử dụng Cmake Mcp trong môi trường được quản lý không?
Xem thêm
Disclaimer: Điểm tin cậy Nerq là đánh giá tự động dựa trên tín hiệu công khai. Đây không phải khuyến nghị hay bảo đảm. Hãy luôn tự xác minh.