Is Codebase State Manager Mcp Safe?
Codebase State Manager Mcp — Nerq Trust Score 75.3/100 (B grade). Based on analysis of 5 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-03-31.
Yes, Codebase State Manager Mcp is safe to use. Codebase State Manager Mcp is a software tool with a Nerq Trust Score of 75.3/100 (B), based on 5 independent data dimensions. It is recommended for use. Security: 0/100. Maintenance: 1/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Machine-readable data (JSON).
Is Codebase State Manager Mcp safe?
YES — Codebase State Manager Mcp has a Nerq Trust Score of 75.3/100 (B). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for use — review the full report below for specific considerations.
What is Codebase State Manager Mcp's trust score?
Codebase State Manager Mcp has a Nerq Trust Score of 75.3/100, earning a B grade. This score is based on 5 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Codebase State Manager Mcp?
Codebase State Manager Mcp's strongest signal is compliance at 100/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.
What is Codebase State Manager Mcp and who maintains it?
| Author | apolosan |
| Category | infrastructure |
| Stars | 1 |
| Source | https://github.com/apolosan/codebase_state_manager_mcp |
| Frameworks | mcp |
| Protocols | mcp · rest |
Regulatory Compliance
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Popular Alternatives in infrastructure
What Is Codebase State Manager Mcp?
Codebase State Manager Mcp is a software tool in the infrastructure category: A sophisticated Model Context Protocol (MCP) server for managing codebase states.. It has 1 GitHub stars. Nerq Trust Score: 75/100 (B).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.
How Nerq Assesses Codebase State Manager Mcp's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Codebase State Manager Mcp performs in each:
- Security (0/100): Codebase State Manager Mcp's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
- Maintenance (1/100): Codebase State Manager 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): Codebase State Manager 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. Based on GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 75.3/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 Codebase State Manager Mcp?
Codebase State Manager Mcp is designed for:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Codebase State Manager Mcp meets the minimum threshold for production use, but we recommend monitoring for security advisories and keeping dependencies up to date. Consider implementing additional guardrails for sensitive workloads.
How to Verify Codebase State Manager Mcp's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Review the repository's security 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 Codebase State Manager Mcp's dependency tree. - Review permissions — Understand what access Codebase State Manager Mcp requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Codebase State Manager 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=codebase_state_manager_mcp - Review the license — Confirm that Codebase State Manager 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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Codebase State Manager Mcp
When evaluating whether Codebase State Manager Mcp is safe, consider these category-specific risks:
Understand how Codebase State Manager Mcp processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Codebase State Manager Mcp's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Codebase State Manager Mcp. Security patches and bug fixes are only effective if you're running the latest version.
If Codebase State Manager 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 Codebase State Manager 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 Codebase State Manager Mcp in violation of its license can expose your organization to legal liability.
Codebase State Manager Mcp and the EU AI Act
Codebase State Manager 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 compliance assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.
Best Practices for Using Codebase State Manager Mcp Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Codebase State Manager Mcp while minimizing risk:
Periodically review how Codebase State Manager Mcp is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Codebase State Manager Mcp and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Codebase State Manager Mcp only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Codebase State Manager Mcp's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Codebase State Manager Mcp is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Codebase State Manager Mcp?
Even well-trusted tools aren't right for every situation. Consider avoiding Codebase State Manager Mcp in these scenarios:
- Scenarios where Codebase State Manager Mcp's specific capabilities exceed your actual needs — simpler tools may be safer
- Air-gapped environments where the tool cannot receive security updates
- Projects with strict regulatory requirements that haven't been explicitly validated
For each scenario, evaluate whether Codebase State Manager Mcp's trust score of 75.3/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.
How Codebase State Manager Mcp Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average Trust Score is 62/100. Codebase State Manager Mcp's score of 75.3/100 is significantly above the category average of 62/100.
This places Codebase State Manager Mcp in the top tier of infrastructure tools that Nerq tracks. Tools scoring this far above average typically demonstrate mature security practices, consistent release cadence, and broad community adoption.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate 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 Codebase State Manager 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, Codebase State Manager 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 security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Codebase State Manager Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=codebase_state_manager_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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Codebase State Manager Mcp are strengthening or weakening over time.
Codebase State Manager Mcp vs Alternatives
In the infrastructure category, Codebase State Manager Mcp scores 75.3/100. It ranks among the top tools in its category. For a detailed comparison, see:
- Codebase State Manager Mcp vs n8n — Trust Score: 78.5/100
- Codebase State Manager Mcp vs langflow — Trust Score: 87.6/100
- Codebase State Manager Mcp vs dify — Trust Score: 79.1/100
Key Takeaways
- Codebase State Manager Mcp has a Trust Score of 75.3/100 (B) and is Nerq Verified.
- Codebase State Manager Mcp meets the minimum threshold for production deployment, though monitoring and additional guardrails are recommended.
- Among infrastructure tools, Codebase State Manager Mcp scores significantly above the category average of 62/100, demonstrating above-average reliability.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Frequently Asked Questions
Is Codebase State Manager Mcp safe to use?
What is Codebase State Manager Mcp's trust score?
What are safer alternatives to Codebase State Manager Mcp?
How often is Codebase State Manager Mcp's safety score updated?
Can I use Codebase State Manager Mcp in a regulated environment?
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.