¿Es Restaurants Seguro?

Restaurants — Nerq Trust Score 59.0/100 (Grado C). Puntuación basada en 5 independent trust signals.

Restaurants es un software tool con un Nerq Trust Score de 59.0/100 (C). Datos de múltiples fuentes públicas incluyendo registros de paquetes, GitHub, NVD, OSV.dev y OpenSSF Scorecard. Última actualización: n/a. Datos legibles por máquina (JSON).

¿Es Restaurants Seguro?

Desglose de Puntuación de Confianza — Restaurants has a Nerq Trust Score of 59.0/100 (C). Measured across 1 independent trust signal.

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

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

Restaurants tiene una Puntuación de Confianza Nerq de 59.0/100, obteniendo un grado C. Esta puntuación se basa en 5 dimensiones medidas independientemente.

Confianza General
59.0

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

La señal más fuerte de Restaurants es confianza general con 59.0/100. No se han detectado vulnerabilidades conocidas.

⚠Puntuación compuesta de confianza: 59.0/100 a través de todas las señales disponibles

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

Autor1301d2eab18e4e6b11ade0a0a5fe28f5008d1eab19a342c9
CategoríaCommunity
Fuentehttps://agentverse.ai/agents/restaurants

Alternativas Populares en community

WritersLogic Business Agents
64.0/100 · C+
agentverse
WritersLogic Developer Agents
64.0/100 · C+
agentverse
WritersLogic Agent Infrastructure
64.0/100 · C+
agentverse
WritersLogic Research Agents
64.0/100 · C+
agentverse
WritersLogic Crypto Agents
64.0/100 · C+
agentverse

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 seguridad vulnerabilities, mantenimiento activity, license cumplimiento, and adopción por la comunidad.

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 dimensiones: Seguridad (known CVEs, dependency vulnerabilities, seguridad policies), Mantenimiento (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, Seguridad and Mantenimiento 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 dimensiones, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).

Who Typically Evaluates Restaurants?

Restaurants is commonly evaluated by:

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:

  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 Restaurants's dependency tree.
  3. Reseña permissions — Understand what access Restaurants requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Restaurants 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=Restaurants
  6. Revisar el/la 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.
  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 Restaurants

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

Data handling

Understand how Restaurants 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 Restaurants's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher seguridad risk.

Update frequency

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

Third-party integrations

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.

License and IP cumplimiento

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:

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for seguridad advisories

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

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 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 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 mantenimiento 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 seguridad and quality. Conversely, a downward trend may signal reduced mantenimiento, 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 — seguridad, mantenimiento, documentación, cumplimiento, and community — has evolved independently, providing granular visibility into which aspects of Restaurants are strengthening or weakening over time.

Restaurants vs Alternativas

In the community category, Restaurants scores 59.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Puntos Clave

Preguntas Frecuentes

¿Es Restaurants Seguro?
Restaurants con un Nerq Trust Score de 59.0/100 (C). Señal más fuerte: confianza general (59.0/100). Puntuación basada en multiple trust dimensiones.
¿Cuál es la puntuación de confianza de Restaurants?
Restaurants: 59.0/100 (C). Puntuación basada en multiple trust dimensiones. Las puntuaciones se actualizan cuando hay nuevos datos. API: GET nerq.ai/v1/preflight?target=Restaurants
¿Cuáles son alternativas más seguras a Restaurants?
En la categoría Community, higher-rated alternatives include WritersLogic Business Agents (64/100), WritersLogic Developer Agents (64/100), WritersLogic Agent Infrastructure (64/100). Restaurants scores 59.0/100.
¿Con qué frecuencia se actualiza la puntuación de Restaurants?
Nerq recomputes Restaurants's trust score as new data becomes available. Current: 59.0/100 (C). API: GET nerq.ai/v1/preflight?target=Restaurants
¿Puedo usar Restaurants en un entorno regulado?
Restaurants: 59.0/100 (C). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
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