Je Code Rag bezpečný?

Code Rag — Nerq Trust Score 43.4/100 (Stupeň E). Na základě analýzy 3 dimenzí důvěryhodnosti je má pozoruhodné bezpečnostní obavy. Naposledy aktualizováno: 2026-03-31.

Buďte opatrní s Code Rag. Code Rag is a software tool se skóre důvěryhodnosti Nerq 43.4/100 (E), based on 3 independent data dimensions. Je pod doporučeným prahem 70. Maintenance: 0/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. Strojově čitelná data (JSON).

Je Code Rag bezpečný?

NE — POUŽÍVEJTE S OPATRNOSTÍ — Code Rag má skóre důvěryhodnosti Nerq 43.4/100 (E). Má podprůměrné signály důvěryhodnosti s významnými mezerami v bezpečnosti, údržbě nebo dokumentaci. Nedoporučeno pro produkční použití bez důkladné ruční kontroly a dalších bezpečnostních opatření.

Bezpečnostní analýza → Zpráva o soukromí {name} →

Jaké je skóre důvěryhodnosti Code Rag?

Code Rag má Nerq skóre důvěryhodnosti 43.4/100 se stupněm E. Toto skóre je založeno na 3 nezávisle měřených dimenzích.

Údržba
0
Dokumentace
0
Popularita
0

Jaká jsou klíčová bezpečnostní zjištění pro Code Rag?

Nejsilnější signál Code Rag je údržba na 0/100. Nebyly zjištěny žádné známé zranitelnosti. Dosud nedosáhl ověřeného prahu Nerq 70+.

Maintenance: 0/100 — low maintenance activity
Documentation: 0/100 — limited documentation
Popularity: 0/100 — 5 stars on pulsemcp

Co je Code Rag a kdo jej spravuje?

Autorhttps://github.com/mirrdhyn/code-rag-mcp
Kategoriecoding
Hvězdičky5
Zdrojhttps://github.com/mirrdhyn/code-rag-mcp

Populární alternativy v coding

Significant-Gravitas/AutoGPT
74.7/100 · B
github
ollama/ollama
73.8/100 · B
github
langchain-ai/langchain
86.4/100 · A
github
x1xhlol/system-prompts-and-models-of-ai-tools
73.8/100 · B
github
anomalyco/opencode
87.9/100 · A
github

What Is Code Rag?

Code Rag is a software tool in the coding category: Code RAG provides semantic code search and similarity matching using vector embeddings.. It has 5 GitHub stars. Nerq Trust Score: 43/100 (E).

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 Code Rag's Safety

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

The overall Trust Score of 43.4/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 Code Rag?

Code Rag is designed for:

Risk guidance: We recommend caution with Code Rag. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Code Rag's Safety Yourself

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

  1. Check the source code — Review the repository security 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 Code Rag's dependency tree.
  3. Recenze permissions — Understand what access Code Rag requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Code Rag 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=Code RAG
  6. Zkontrolujte license — Confirm that Code Rag'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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Code Rag

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

Data handling

Understand how Code Rag processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Code Rag's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Code Rag. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Code Rag 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 compliance

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

Best Practices for Using Code Rag Safely

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

Conduct regular audits

Periodically review how Code Rag is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Code Rag and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Code Rag?

Even promising tools aren't right for every situation. Consider avoiding Code Rag in these scenarios:

skóre důvěryhodnosti

For each scenario, evaluate whether Code Rag 43.4/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Code Rag Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Trust Score is 62/100. Code Rag's score of 43.4/100 is below the category average of 62/100.

This suggests that Code Rag trails behind many comparable coding tools. Organizations with strict security 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 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 Code Rag 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, Code Rag'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 Code Rag's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Code RAG&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 Code Rag are strengthening or weakening over time.

Code Rag vs Alternatives

V kategorii coding, Code Rag získal skóre 43.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Hlavní závěry

Často kladené otázky

Je Code Rag bezpečný k použití?
Buďte opatrní. Code RAG má skóre důvěryhodnosti Nerq 43.4/100 (E). Nejsilnější signál: údržba (0/100). Skóre založeno na maintenance (0/100), popularity (0/100), documentation (0/100).
Jaké je skóre důvěryhodnosti Code Rag?
Code RAG: 43.4/100 (E). Skóre založeno na: maintenance (0/100), popularity (0/100), documentation (0/100). Skóre se aktualizují, jakmile jsou k dispozici nová data. API: GET nerq.ai/v1/preflight?target=Code RAG
Jaké jsou bezpečnější alternativy k Code Rag?
V kategorii coding, lépe hodnocené alternativy zahrnují Significant-Gravitas/AutoGPT (75/100), ollama/ollama (74/100), langchain-ai/langchain (86/100). Code RAG získal skóre 43.4/100.
How often is Code Rag's safety score updated?
Nerq continuously monitors Code Rag and updates its trust score as new data becomes available. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 43.4/100 (E), last verified 2026-03-31. API: GET nerq.ai/v1/preflight?target=Code RAG
Mohu použít Code Rag v regulovaném prostředí?
Code Rag 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: Skóre důvěryhodnosti Nerq jsou automatizovaná hodnocení založená na veřejně dostupných signálech. Nejsou doporučením ani zárukou. Vždy proveďte vlastní ověření.

We use cookies for analytics and caching. Soukromí Policy