Este My Opencode sigur?
My Opencode — Nerq Trust Score 75.4/100 (Nota B). Pe baza analizei a 5 dimensiuni de încredere, este în general sigur, dar cu unele preocupări. Ultima actualizare: 2026-04-05.
Da, My Opencode este sigur de utilizat. My Opencode este un software tool cu un Scor de Încredere Nerq de 75.4/100 (B), based on 5 dimensiuni independente de date. It is recommended for use. Securitate: 0/100. Mentenanță: 1/100. Popularitate: 0/100. Date provenite din multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Ultima actualizare: 2026-04-05. Date citibile de mașină (JSON).
Este My Opencode sigur?
DA — My Opencode are un Scor de Încredere Nerq de 75.4/100 (B). Îndeplinește pragul de încredere Nerq cu semnale puternice în securitate, mentenanță și adoptare comunitară. Recommended for use — consultați raportul complet de mai jos pentru considerații specifice.
Care este scorul de încredere al My Opencode?
My Opencode are un Nerq Trust Score de 75.4/100 cu nota B. Acest scor se bazează pe 5 dimensiuni măsurate independent, inclusiv securitate, întreținere și adopție comunitară.
Care sunt principalele constatări de securitate pentru My Opencode?
Cel mai puternic semnal al My Opencode este conformitate la 100/100. Nu au fost detectate vulnerabilități cunoscute. It meets the Nerq Verified threshold of 70+.
Ce este My Opencode și cine îl întreține?
| Autor | jabing |
| Categorie | coding |
| Sursă | https://github.com/jabing/my-opencode |
Conformitate reglementară
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Alternative populare în coding
My Opencode pe alte platforme
Același dezvoltator/companie în alte registre:
What Is My Opencode?
My Opencode is a software tool in the coding category: One-click deployment of 6-role professional AI development team framework.. Nerq Trust Score: 75/100 (B).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including securitate vulnerabilities, mentenanță activity, license conformitate, and adoptare comunitară.
How Nerq Assesses My Opencode's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiuni. Here is how My Opencode performs in each:
- Securitate (0/100): My Opencode's securitate posture is poor. This score factors in known CVEs, dependency vulnerabilities, securitate policy presence, and code signing practices.
- Mentenanță (1/100): My Opencode 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 documentație, usage examples, and contribution guidelines.
- Compliance (100/100): My Opencode is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Bazat pe GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 75.4/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 My Opencode?
My Opencode is designed for:
- Developers and teams working with coding tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: My Opencode meets the minimum threshold for production use, but we recommend monitoring for securitate advisories and keeping dependencies up to date. Consider implementing additional guardrails for sensitive workloads.
How to Verify My Opencode's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Verificați repository's securitate policy, open issues, and recent commits for signs of active mentenanță.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in My Opencode's dependency tree. - Recenzie permissions — Understand what access My Opencode requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run My Opencode 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=my-opencode - Verificați license — Confirm that My Opencode'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 securitate concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with My Opencode
When evaluating whether My Opencode is safe, consider these category-specific risks:
Understand how My Opencode processes, stores, and transmits your data. Verificați tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check My Opencode's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher securitate risk.
Regularly check for updates to My Opencode. Securitate patches and bug fixes are only effective if you're running the latest version.
If My Opencode 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 My Opencode's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using My Opencode in violation of its license can expose your organization to legal liability.
My Opencode and the EU AI Act
My Opencode 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 conformitate assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal conformitate.
Best Practices for Using My Opencode Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from My Opencode while minimizing risk:
Periodically review how My Opencode is used in your workflow. Check for unexpected behavior, permissions drift, and conformitate with your securitate policies.
Ensure My Opencode and all its dependencies are running the latest stable versions to benefit from securitate patches.
Grant My Opencode only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to My Opencode's securitate advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how My Opencode is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid My Opencode?
Even well-trusted tools aren't right for every situation. Consider avoiding My Opencode in these scenarios:
- Scenarios where My Opencode's specific capabilities exceed your actual needs — simpler tools may be safer
- Air-gapped environments where the tool cannot receive securitate updates
- Projects with strict regulatory requirements that haven't been explicitly validated
For each scenario, evaluate whether My Opencode de 75.4/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.
How My Opencode 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. My Opencode's score of 75.4/100 is significantly above the category average of 62/100.
This places My Opencode in the top tier of coding tools that Nerq tracks. Tools scoring this far above average typically demonstrate mature securitate practices, consistent release cadence, and broad adoptare comunitară.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderat 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 My Opencode 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 mentenanță patterns change, My Opencode'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 securitate and quality. Conversely, a downward trend may signal reduced mentenanță, growing technical debt, or unresolved vulnerabilities. To track My Opencode's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=my-opencode&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 — securitate, mentenanță, documentație, conformitate, and community — has evolved independently, providing granular visibility into which aspects of My Opencode are strengthening or weakening over time.
My Opencode vs Alternative
În categoria coding, My Opencode a obținut scorul 75.4/100. It ranks among the top tools in its category. For a detailed comparison, see:
- My Opencode vs AutoGPT — Trust Score: 74.7/100
- My Opencode vs ollama — Trust Score: 73.8/100
- My Opencode vs langchain — Trust Score: 86.4/100
Concluzii principale
- My Opencode are un Scor de Încredere de 75.4/100 (B) and is Nerq Verified.
- My Opencode meets the minimum threshold for production deployment, though monitoring and additional guardrails are recommended.
- Among coding tools, My Opencode 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.
Întrebări frecvente
Este My Opencode sigur de utilizat?
Ce este My Opencode's trust score?
Care sunt alternativele mai sigure la My Opencode?
How often is My Opencode's safety score updated?
Pot folosi My Opencode într-un mediu reglementat?
Disclaimer: Scorurile de încredere Nerq sunt evaluări automatizate bazate pe semnale disponibile public. Nu sunt recomandări sau garanții. Efectuați întotdeauna propria verificare.