¿Es Getweb Seguro?

Getweb — Nerq Trust Score 44.7/100 (Grado E). Basado en el análisis de 3 dimensiones de confianza, se tiene preocupaciones de seguridad notables. Última actualización: 2026-04-05.

Ten precaución con Getweb. Getweb es un software tool con un Nerq Trust Score de 44.7/100 (E), basado en 3 dimensiones de datos independientes. Por debajo del umbral verificado de Nerq Mantenimiento: 0/100. Popularidad: 0/100. Datos de múltiples fuentes públicas incluyendo registros de paquetes, GitHub, NVD, OSV.dev y OpenSSF Scorecard. Última actualización: 2026-04-05. Datos legibles por máquina (JSON).

¿Es Getweb Seguro?

NO — USE WITH CAUTION — Getweb has a Nerq Trust Score of 44.7/100 (E). Tiene señales de confianza por debajo del promedio con brechas significativas in seguridad, mantenimiento, or documentación. Not recommended for production use without thorough manual review and additional seguridad measures.

Análisis de Seguridad → Informe de Privacidad de Getweb →

¿Cuál es la puntuación de confianza de Getweb?

Getweb tiene una Puntuación de Confianza Nerq de 44.7/100, obteniendo un grado E. Esta puntuación se basa en 3 dimensiones medidas independientemente.

Mantenimiento
0
Documentación
0
Popularidad
0

¿Cuáles son los hallazgos de seguridad clave de Getweb?

La señal más fuerte de Getweb es mantenimiento con 0/100. No se han detectado vulnerabilidades conocidas. Aún no ha alcanzado el umbral verificado de Nerq de 70+.

Mantenimiento: 0/100 — baja actividad de mantenimiento
Documentación: 0/100 — documentación limitada
Popularidad: 0/100 — 13 estrellas en pulsemcp

¿Qué es Getweb y quién lo mantiene?

Autorhttps://github.com/ivan-mezentsev/mcp-getweb
CategoríaResearch
Estrellas13
Fuentehttps://github.com/ivan-mezentsev/mcp-getweb

Alternativas Populares en research

binary-husky/gpt_academic
71.3/100 · B
github
hiyouga/LlamaFactory
89.1/100 · A
github
unslothai/unsloth
86.6/100 · A
github
stanford-oval/storm
73.8/100 · B
github
assafelovic/gpt-researcher
73.8/100 · B
github

What Is Getweb?

Getweb is a software tool in the research category: GetWeb integrates multiple APIs for reliable web research and information retrieval.. It has 13 GitHub stars. Nerq Trust Score: 45/100 (E).

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 Getweb's Safety

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

The overall Trust Score of 44.7/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 Getweb?

Getweb is designed for:

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

How to Verify Getweb'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 el/la repository seguridad policy, open issues, and recent commits for signs of active mantenimiento.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Getweb's dependency tree.
  3. Reseña permissions — Understand what access Getweb requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Getweb 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=GetWeb
  6. Revisar el/la license — Confirm that Getweb'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 seguridad concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Getweb

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

Data handling

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

Dependency seguridad

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

Update frequency

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

Third-party integrations

If Getweb 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 cumplimiento

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

Best Practices for Using Getweb Safely

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

Conduct regular audits

Periodically review how Getweb is used in your workflow. Check for unexpected behavior, permissions drift, and cumplimiento with your seguridad policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for seguridad advisories

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

When Should You Avoid Getweb?

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

For each scenario, evaluate whether Getweb's trust score of 44.7/100 meets your organization's risk tolerance. We recommend running a manual seguridad assessment alongside the automated Nerq score.

How Getweb Compares to Industry Standards

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

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

Getweb vs Alternativas

In the research category, Getweb scores 44.7/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Puntos Clave

Preguntas Frecuentes

¿Es Getweb safe to use?
Tener precaución. GetWeb has a Nerq Trust Score of 44.7/100 (E). Señal más fuerte: mantenimiento (0/100). Puntuación basada en mantenimiento (0/100), popularidad (0/100), documentación (0/100).
¿Qué es Getweb's puntuación de confianza?
GetWeb: 44.7/100 (E). Puntuación basada en: mantenimiento (0/100), popularidad (0/100), documentación (0/100). Las puntuaciones se actualizan cuando hay nuevos datos. API: GET nerq.ai/v1/preflight?target=GetWeb
What are safer alternatives to Getweb?
En la categoría Research, higher-rated alternatives include binary-husky/gpt_academic (71/100), hiyouga/LlamaFactory (89/100), unslothai/unsloth (87/100). GetWeb scores 44.7/100.
How often is Getweb's safety score updated?
Nerq continuously monitors Getweb and updates its trust score as new data becomes available. Datos obtenidos de múltiples fuentes públicas incluyendo registros de paquetes, GitHub, NVD, OSV.dev y OpenSSF Scorecard. Current: 44.7/100 (E), last verificado 2026-04-05. API: GET nerq.ai/v1/preflight?target=GetWeb
Can I use Getweb in a regulated environment?
Getweb has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

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.

Usamos cookies para análisis y caché. Privacidad