¿Es Domshell Seguro?

Ten precaución con Domshell. Domshell is a software tool with a Nerq Puntuación de Confianza de 38.0/100 (E), based on 3 independent data dimensions. It is below the recommended threshold of 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Última actualización: 2026-03-26. Datos legibles por máquina (JSON).

¿Es Domshell Seguro?

NO — USE WITH CAUTION — Domshell tiene una Puntuación de Confianza Nerq de 38.0/100 (E). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

Desglose de Puntuación de Confianza

Mantenimiento
0
Documentación
0
Popularidad
0

Hallazgos Clave

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

Detalles

Autorhttps://github.com/apireno/domshell/tree/HEAD/mcp-server
Categoríadevops
Estrellas6
Fuentehttps://github.com/apireno/domshell/tree/HEAD/mcp-server

Alternativas Populares en devops

ansible/ansible
84.3/100 · A
github
FlowiseAI/Flowise
76.9/100 · B
github
continuedev/continue
84.4/100 · A
github
wshobson/agents
88.7/100 · A
github
nrwl/nx
85.9/100 · A
github

What Is Domshell?

Domshell is a DevOps tool: Chrome extension that maps browser DOM into a virtual filesystem navigable with shell commands.. It has 6 GitHub stars. Nerq Trust Puntuación: 38/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 Domshell's Safety

Nerq's Puntuación de Confianza is calculated from 13+ independent signals aggregated into five dimensions. Here is how Domshell performs in each:

The overall Puntuación de Confianza de 38.0/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 Domshell?

Domshell is designed for:

Risk guidance: We recommend caution with Domshell. 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 Domshell's Safety Yourself

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

  1. Check the source code — Revisar 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 Domshell's dependency tree.
  3. Revisar permissions — Understand what access Domshell requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Domshell 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=DomShell
  6. Revisar the license — Confirm that Domshell'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 Domshell

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

Data handling

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

Dependency security

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

Update frequency

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

Third-party integrations

If Domshell 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 Domshell's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Domshell in violation of its license can expose your organization to legal liability.

Best Practices for Using Domshell Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Domshell?

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

La puntuación de confianza de

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

How Domshell Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Puntuación de Confianza is 63/100. Domshell's score of 38.0/100 is below the category average of 63/100.

This suggests that Domshell trails behind many comparable DevOps 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.

Puntuación de Confianza History

Nerq continuously monitors Domshell and recalculates its Puntuación de Confianza 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, Domshell'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 Domshell's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=DomShell&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 Domshell are strengthening or weakening over time.

Domshell vs Alternatives

In the devops category, Domshell tiene una puntuación de 38.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Puntos Clave

Preguntas Frecuentes

¿Es Domshell safe to use?
Tener precaución. DomShell tiene una Puntuación de Confianza Nerq de 38.0/100 (E). Señal más fuerte: mantenimiento (0/100). Score based on maintenance (0/100), popularity (0/100), documentation (0/100).
¿Cuál es la puntuación de confianza de Domshell?
DomShell: 38.0/100 (E). Score based on: maintenance (0/100), popularity (0/100), documentation (0/100). Las puntuaciones se actualizan con nuevos datos. API: GET nerq.ai/v1/preflight?target=DomShell
¿Cuáles son alternativas más seguras a Domshell?
In the devops category, higher-rated alternatives include ansible/ansible (84/100), FlowiseAI/Flowise (77/100), continuedev/continue (84/100). DomShell tiene una puntuación de 38.0/100.
How often is Domshell's safety score updated?
Nerq continuously monitors Domshell 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: 38.0/100 (E), last verified 2026-03-26. API: GET nerq.ai/v1/preflight?target=DomShell
Can I use Domshell in a regulated environment?
Domshell 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: 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.