Ist Restaurants sicher?
Restaurants — Nerq Trust Score 59.0/100 (Note C). Bewertung basierend auf 5 independent trust signals.
Restaurants ist ein software tool mit einem Nerq-Vertrauenswert von 59.0/100 (C). Daten von mehreren öffentlichen Quellen einschließlich Paketregistern, GitHub, NVD, OSV.dev und OpenSSF Scorecard. Zuletzt aktualisiert: n/a. Maschinenlesbare Daten (JSON).
Ist Restaurants sicher?
Vertrauensbewertung im Detail — Restaurants has a Nerq Trust Score of 59.0/100 (C). Measured across 1 independent trust signal.
Was ist die Vertrauensbewertung von Restaurants?
Restaurants hat eine Nerq-Vertrauensbewertung von 59.0/100 und erhält die Note C. Diese Bewertung basiert auf 5 unabhängig gemessenen Dimensionen.
Was sind die wichtigsten Sicherheitsergebnisse für Restaurants?
Das stärkste Signal von Restaurants ist gesamtvertrauen mit 59.0/100. Es wurden keine bekannten Schwachstellen erkannt.
Was ist Restaurants und wer pflegt es?
| Autor | 1301d2eab18e4e6b11ade0a0a5fe28f5008d1eab19a342c9 |
| Kategorie | Community |
| Quelle | https://agentverse.ai/agents/restaurants |
Beliebte Alternativen in community
What Is Restaurants?
Restaurants is a software tool in the community category: Where to eat by city, cuisine and budget: local-style areas, typical dishes and price bands, plus tips to avoid tourist traps. Not live menus or bookings.. Nerq Trust Score: 59/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including Sicherheit vulnerabilities, Wartung activity, license Konformität, and Community-Akzeptanz.
How Nerq Assesses Restaurants's Safety
Nerq evaluates every software tool across 13+ independent trust signals drawn from public sources including GitHub, NVD, OSV.dev, OpenSSF Scorecard, and package registries. These signals are grouped into five core Dimensionen: Sicherheit (known CVEs, dependency vulnerabilities, Sicherheit policies), Wartung (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 jurisdictions), and Community (stars, forks, downloads, ecosystem integrations).
Restaurants receives an overall Trust Score of 59.0/100 (C). This is a measured composite, not a suitability judgment.
Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=Restaurants
Each dimension is weighted according to its importance for the tool's category. For example, Sicherheit and Wartung carry higher weight for tools that handle sensitive data or execute code, while Community and Documentation are weighted more heavily for developer-facing libraries and frameworks. This ensures that Restaurants's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five Dimensionen, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).
Who Typically Evaluates Restaurants?
Restaurants is commonly evaluated by:
- Developers and teams working with community tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Restaurants's measured signals (the trust signals above) 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 Restaurants's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Überprüfen Sie das/die repository Sicherheit policy, open issues, and recent commits for signs of active Wartung.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Restaurants's dependency tree. - Bewertung permissions — Understand what access Restaurants requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Restaurants 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=Restaurants - Überprüfen Sie das/die license — Confirm that Restaurants'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 Sicherheit concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Restaurants
When evaluating whether Restaurants is safe, consider these category-specific risks:
Understand how Restaurants processes, stores, and transmits your data. Überprüfen Sie das/die tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Restaurants's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher Sicherheit risk.
Regularly check for updates to Restaurants. Sicherheit patches and bug fixes are only effective if you're running the latest version.
If Restaurants 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 Restaurants's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Restaurants in violation of its license can expose your organization to legal liability.
Best Practices for Using Restaurants Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Restaurants while minimizing risk:
Periodically review how Restaurants is used in your workflow. Check for unexpected behavior, permissions drift, and Konformität with your Sicherheit policies.
Ensure Restaurants and all its dependencies are running the latest stable versions to benefit from Sicherheit patches.
Grant Restaurants only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Restaurants's Sicherheit advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Restaurants is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Restaurants
Nerq's signals are one input. In the following situations, evaluate Restaurants'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 Restaurants's measured trust score of 59.0/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Restaurants is suitable for any particular use.
How Restaurants Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among community tools, the average Trust Score is 62/100. Restaurants's score of 59.0/100 is near the category average of 62/100.
This places Restaurants in line with the typical community tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.
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 Restaurants 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 Wartung patterns change, Restaurants'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 Sicherheit and quality. Conversely, a downward trend may signal reduced Wartung, growing technical debt, or unresolved vulnerabilities. To track Restaurants's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Restaurants&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 — Sicherheit, Wartung, Dokumentation, Konformität, and community — has evolved independently, providing granular visibility into which aspects of Restaurants are strengthening or weakening over time.
Restaurants vs Alternativen
In the community category, Restaurants scores 59.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Restaurants vs WritersLogic Business Agents — Trust Score: 64.0/100
- Restaurants vs WritersLogic Developer Agents — Trust Score: 64.0/100
- Restaurants vs WritersLogic Agent Infrastructure — Trust Score: 64.0/100
Wichtigste Punkte
- Restaurants has a measured Nerq Trust Score of 59.0/100 (C) — a composite of independent signals, not a suitability judgment.
- Among community tools, Restaurants scores near the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — Sicherheit, Wartung, Dokumentation, Konformität, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Häufig gestellte Fragen
Ist Restaurants sicher?
Was ist die Vertrauensbewertung von Restaurants?
Was sind sicherere Alternativen zu Restaurants?
Wie oft wird die Sicherheitsbewertung von Restaurants aktualisiert?
Kann ich Restaurants in einer regulierten Umgebung verwenden?
Siehe auch
Disclaimer: Nerq-Vertrauensbewertungen sind automatisierte Bewertungen basierend auf öffentlich verfügbaren Signalen. Sie sind keine Empfehlungen oder Garantien. Führen Sie immer Ihre eigene Sorgfaltsprüfung durch.