¿Es Oh My Claudecode Seguro?
Oh My Claudecode — Nerq Trust Score 72.0/100 (Grado B). Puntuación basada en 5 independent trust signals.
Oh My Claudecode es un software tool con un Nerq Trust Score de 72.0/100 (B), basado en 5 dimensiones de datos independientes. Seguridad: 1/100. Mantenimiento: 1/100. Popularidad: 1/100. Datos de múltiples fuentes públicas incluyendo registros de paquetes, GitHub, NVD, OSV.dev y OpenSSF Scorecard. Última actualización: n/a. Datos legibles por máquina (JSON).
¿Es Oh My Claudecode Seguro?
Desglose de Puntuación de Confianza — Oh My Claudecode has a Nerq Trust Score of 72.0/100 (B). Measured across 5 independent trust signals.
¿Cuál es la puntuación de confianza de Oh My Claudecode?
Oh My Claudecode tiene una Puntuación de Confianza Nerq de 72.0/100, obteniendo un grado B. Esta puntuación se basa en 5 dimensiones medidas independientemente.
¿Cuáles son los hallazgos de seguridad clave de Oh My Claudecode?
La señal más fuerte de Oh My Claudecode es cumplimiento con 100/100. No se han detectado vulnerabilidades conocidas.
¿Qué es Oh My Claudecode y quién lo mantiene?
| Autor | Yeachan-Heo |
| Categoría | Infrastructure |
| Estrellas | 6,933 |
| Fuente | https://github.com/Yeachan-Heo/oh-my-claudecode |
| Frameworks | openai · anthropic · mcp |
| Protocols | rest |
Cumplimiento Regulatorio
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Alternativas Populares en infrastructure
Oh My Claudecode en Otras Plataformas
Mismo desarrollador/empresa en otros registros:
What Is Oh My Claudecode?
Oh My Claudecode is a software tool in the infrastructure category: Teams-first Multi-agent orchestration for Claude Code. It has 6,933 GitHub stars. Nerq Trust Score: 72/100 (B).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including seguridad vulnerabilities, mantenimiento activity, license cumplimiento, and adopción por la comunidad.
How Nerq Assesses Oh My Claudecode's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiones. Here is how Oh My Claudecode performs in each:
- Seguridad (1/100): Oh My Claudecode's seguridad posture is poor. This score factors in known CVEs, dependency vulnerabilities, seguridad policy presence, and code signing practices.
- Mantenimiento (1/100): Oh My Claudecode 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 documentación, usage examples, and contribution guidelines.
- Compliance (100/100): Oh My Claudecode is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (1/100): Community adoption is limited. Basado en GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 72.0/100 (B) 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 Oh My Claudecode?
Oh My Claudecode is commonly evaluated by:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Oh My Claudecode's measured signals (seguridad 1/100, mantenimiento 1/100, documentación 1/100, community 1/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 Oh My Claudecode's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Revisar el/la repository's seguridad policy, open issues, and recent commits for signs of active mantenimiento.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Oh My Claudecode's dependency tree. - Reseña permissions — Understand what access Oh My Claudecode requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Oh My Claudecode 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=Yeachan-Heo/oh-my-claudecode - Revisar el/la license — Confirm that Oh My Claudecode'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 seguridad concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Oh My Claudecode
When evaluating whether Oh My Claudecode is safe, consider these category-specific risks:
Understand how Oh My Claudecode processes, stores, and transmits your data. Revisar el/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Oh My Claudecode's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher seguridad risk.
Regularly check for updates to Oh My Claudecode. Seguridad patches and bug fixes are only effective if you're running the latest version.
If Oh My Claudecode 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 Oh My Claudecode's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Oh My Claudecode in violation of its license can expose your organization to legal liability.
Best Practices for Using Oh My Claudecode Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Oh My Claudecode while minimizing risk:
Periodically review how Oh My Claudecode is used in your workflow. Check for unexpected behavior, permissions drift, and cumplimiento with your seguridad policies.
Ensure Oh My Claudecode and all its dependencies are running the latest stable versions to benefit from seguridad patches.
Grant Oh My Claudecode only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Oh My Claudecode's seguridad advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Oh My Claudecode is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Oh My Claudecode
Nerq's signals are one input. In the following situations, evaluate Oh My Claudecode'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 Oh My Claudecode's measured trust score of 72.0/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Oh My Claudecode is suitable for any particular use.
How Oh My Claudecode 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. Oh My Claudecode's score of 72.0/100 is above the category average of 62/100.
This positions Oh My Claudecode favorably among infrastructure tools. While it outperforms the average, there is still room for improvement in certain trust dimensiones.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderado 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 Oh My Claudecode 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 mantenimiento patterns change, Oh My Claudecode'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 seguridad and quality. Conversely, a downward trend may signal reduced mantenimiento, growing technical debt, or unresolved vulnerabilities. To track Oh My Claudecode's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Yeachan-Heo/oh-my-claudecode&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 — seguridad, mantenimiento, documentación, cumplimiento, and community — has evolved independently, providing granular visibility into which aspects of Oh My Claudecode are strengthening or weakening over time.
Oh My Claudecode vs Alternativas
In the infrastructure category, Oh My Claudecode scores 72.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Oh My Claudecode vs n8n — Trust Score: 69.1/100
- Oh My Claudecode vs langflow — Trust Score: 77.0/100
- Oh My Claudecode vs dify — Trust Score: 69.7/100
Puntos Clave
- Oh My Claudecode has a measured Nerq Trust Score of 72.0/100 (B) — a composite of independent signals, not a suitability judgment.
- Among infrastructure tools, Oh My Claudecode scores above the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — seguridad, mantenimiento, documentación, cumplimiento, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Preguntas Frecuentes
¿Es Oh My Claudecode Seguro?
¿Cuál es la puntuación de confianza de Oh My Claudecode?
¿Cuáles son alternativas más seguras a Oh My Claudecode?
¿Con qué frecuencia se actualiza la puntuación de Oh My Claudecode?
¿Puedo usar Oh My Claudecode en un entorno regulado?
Ver también
Disclaimer: Las puntuaciones de confianza de Nerq son evaluaciones automatizadas basadas en señales disponibles públicamente. No son respaldos ni garantías. Siempre realice su propia diligencia debida.