Är Getweb säker?

Getweb — Nerq Förtroendepoäng 44.7/100 (Betyg E). Baserat på analys av 3 tillitsdimensioner bedöms det som har anmärkningsvärda säkerhetsproblem. Senast uppdaterad: 2026-04-02.

Var försiktig med Getweb. Getweb is a software tool med ett Nerq-förtroendepoäng på 44.7/100 (E), based on 3 independent data dimensions. Ligger under den rekommenderade gränsen på 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-04-02. Maskinläsbar data (JSON).

Är Getweb säker?

NEJ — ANVÄND MED FÖRSIKTIGHET — Getweb har ett Nerq-förtroendepoäng på 44.7/100 (E). Har lägre än genomsnittliga förtroendesignaler med betydande luckor i säkerhet, underhåll eller dokumentation. Rekommenderas inte för produktionsanvändning utan noggrann manuell granskning och ytterligare säkerhetsåtgärder.

Säkerhetsanalys → {name} integritetsrapport →

Vad är Getwebs förtroendepoäng?

Getweb har ett Nerq-förtroendepoäng på 44.7/100, earning a E grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.

Underhåll
0
Dokumentation
0
Popularitet
0

Vilka är de viktigaste säkerhetsresultaten för Getweb?

Getweb's strongest signal is underhåll at 0/100. No kända sårbarheter have been detected. It has not yet reached the Nerq Verified threshold of 70+.

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

Vad är Getweb och vem underhåller det?

Utvecklarehttps://github.com/ivan-mezentsev/mcp-getweb
Kategoriresearch
Stjärnor13
Källahttps://github.com/ivan-mezentsev/mcp-getweb

Populära alternativ inom 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 Förtroendepoäng: 45/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 Getweb's Safety

Nerq's Förtroendepoäng is calculated from 13+ independent signals aggregated into five dimensions. Here is how Getweb performs in each:

The overall Förtroendepoäng 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 security, maintenance, 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 — 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 kända sårbarheter in Getweb's dependency tree.
  3. Recension 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. Granska 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 security 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. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Getweb's dependency tree for kända sårbarheter. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Getweb. Security 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 compliance

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 compliance with your security policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

Subscribe to Getweb'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 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:

förtroendepoängen för

For each scenario, evaluate whether Getweb är 44.7/100 meets your organization's risk tolerance. We recommend running a manual security 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 Förtroendepoäng 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 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.

Förtroendepoäng History

Nerq continuously monitors Getweb and recalculates its Förtroendepoäng 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, 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 security and quality. Conversely, a downward trend may signal reduced maintenance, 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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Getweb are strengthening or weakening over time.

Getweb vs Alternatives

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

Viktigaste slutsatser

Vanliga frågor

Är Getweb säker att använda?
Var försiktig. GetWeb har ett Nerq-förtroendepoäng på 44.7/100 (E). Starkaste signalen: underhåll (0/100). Poäng baserad på maintenance (0/100), popularity (0/100), documentation (0/100).
Vad är Getweb's trust score?
GetWeb: 44.7/100 (E). Poäng baserad på: maintenance (0/100), popularity (0/100), documentation (0/100). Poäng uppdateras när ny data finns tillgänglig. API: GET nerq.ai/v1/preflight?target=GetWeb
Vilka säkrare alternativ finns till Getweb?
In the research category, högre betygsatta alternativ inkluderar 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. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 44.7/100 (E), last verified 2026-04-02. API: GET nerq.ai/v1/preflight?target=GetWeb
Kan jag använda Getweb i en reglerad miljö?
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

Disclaimer: Nerqs förtroendepoäng är automatiserade bedömningar baserade på offentligt tillgängliga signaler. De utgör inte rekommendationer eller garantier. Gör alltid din egen verifiering.

We use cookies for analytics and caching. Integritet Policy