Er Rami Levy trygt?

Rami Levy — Nerq Trust Score 44.7/100 (Karakter E). Poeng basert på 3 independent trust signals.

Rami Levy er en software tool har en Nerq-tillitspoeng på 44.7/100 (E), based on 3 uavhengige datadimensjoner. Vedlikehold: 0/100. Popularitet: 0/100. Data hentet fra flere offentlige kilder inkludert pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sist oppdatert: n/a. Maskinlesbare data (JSON).

Er Rami Levy trygt?

Tillitspoeng detaljer — Rami Levy har en Nerq-tillitspoeng på 44.7/100 (E). Measured across 3 independent trust signals.

Sikkerhetsanalyse → Rami Levy personvernrapport →

Hva er tillitspoengene til Rami Levy?

Rami Levy har en Nerq-tillitspoeng på 44.7/100 med karakteren E. Denne poengsummen er basert på 3 uavhengig målte dimensjoner, inkludert sikkerhet, vedlikehold og samfunnsadopsjon.

Vedlikehold
0
Dokumentasjon
0
Popularitet
0

Hva er de viktigste sikkerhetsfunnene for Rami Levy?

Rami Levys sterkeste signal er vedlikehold på 0/100. Ingen kjente sårbarheter er funnet.

⚠Vedlikehold: 0/100 — lav vedlikeholdsaktivitet
⚠Dokumentasjon: 0/100 — begrenset dokumentasjon
⚠Popularitet: 0/100 — 10 stjerner på pulsemcp

Hva er Rami Levy og hvem vedlikeholder det?

Utviklerhttps://github.com/shilomagen/rami-levy-mcp
KategoriCommerce
Stjerner10
Kildehttps://github.com/shilomagen/rami-levy-mcp

Populære alternativer i commerce

tomaspavlin/rohlik-mcp
61.4/100 · C
github
Magento 2
46.5/100 · D
pulsemcp
Hazrat-Ali9/Flight-Ticket-Booking
55.2/100 · D
github
ystemsrx/smart-shop
55.2/100 · D
github
MercadoLibre
42.5/100 · E
pulsemcp

What Is Rami Levy?

Rami Levy is a software tool in the commerce category: Enables product searches, shopping cart management, and checkout for Rami Levy online grocery platform.. It has 10 GitHub stars. Nerq Trust Score: 45/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhet vulnerabilities, vedlikehold activity, license samsvar, and fellesskapsadopsjon.

How Nerq Assesses Rami Levy's Safety

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

The overall Trust Score of 44.7/100 (E) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.

Who Typically Evaluates Rami Levy?

Rami Levy is commonly evaluated by:

How to read the signals: Rami Levy's measured signals (vedlikehold 0/100, dokumentasjon 0/100, community 0/100) 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 Rami Levy's Safety Yourself

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

  1. Check the source code — Gjennomgå repository sikkerhet policy, open issues, and recent commits for signs of active vedlikehold.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for kjente sårbarheter in Rami Levy's dependency tree.
  3. Anmeldelse permissions — Understand what access Rami Levy requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Rami Levy 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=Rami Levy
  6. Gjennomgå license — Confirm that Rami Levy'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 sikkerhet concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Rami Levy

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

Data handling

Understand how Rami Levy processes, stores, and transmits your data. Gjennomgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sikkerhet

Check Rami Levy's dependency tree for kjente sårbarheter. Tools with outdated or unmaintained dependencies pose a higher sikkerhet risk.

Update frequency

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

Third-party integrations

If Rami Levy 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 samsvar

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

Best Practices for Using Rami Levy Safely

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

Conduct regular audits

Periodically review how Rami Levy is used in your workflow. Check for unexpected behavior, permissions drift, and samsvar with your sikkerhet policies.

Keep dependencies updated

Ensure Rami Levy and all its dependencies are running the latest stable versions to benefit from sikkerhet patches.

Follow least privilege

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

Monitor for sikkerhet advisories

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

Situations That Warrant Independent Review of Rami Levy

Nerq's signals are one input. In the following situations, evaluate Rami Levy's measured signals against your own requirements before making a decision:

For each situation, compare Rami Levy's measured trust score of 44.7/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Rami Levy is suitable for any particular use.

How Rami Levy Compares to Industry Standards

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

This suggests that Rami Levy trails behind many comparable commerce tools. Organizations with strict sikkerhet 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 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 Rami Levy 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 vedlikehold patterns change, Rami Levy'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 sikkerhet and quality. Conversely, a downward trend may signal reduced vedlikehold, growing technical debt, or unresolved vulnerabilities. To track Rami Levy's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Rami Levy&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 — sikkerhet, vedlikehold, dokumentasjon, samsvar, and community — has evolved independently, providing granular visibility into which aspects of Rami Levy are strengthening or weakening over time.

Rami Levy vs Alternativer

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

Viktigste punkter

Ofte stilte spørsmål

Er Rami Levy trygt?
Rami Levy har en Nerq-tillitspoeng på 44.7/100 (E). Sterkeste signal: vedlikehold (0/100). Poeng basert på Vedlikehold (0/100), Popularitet (0/100), Dokumentasjon (0/100).
Hva er tillitspoengene til Rami Levy?
Rami Levy: 44.7/100 (E). Poeng basert på Vedlikehold (0/100), Popularitet (0/100), Dokumentasjon (0/100). Poeng oppdateres når nye data er tilgjengelige. API: GET nerq.ai/v1/preflight?target=Rami Levy
Hva er tryggere alternativer til Rami Levy?
I kategorien Commerce, higher-rated alternatives include tomaspavlin/rohlik-mcp (61/100), Magento 2 (46/100), Hazrat-Ali9/Flight-Ticket-Booking (55/100). Rami Levy scores 44.7/100.
Hvor ofte oppdateres Rami Levys sikkerhetspoeng?
Nerq recomputes Rami Levy's trust score as new data becomes available. Current: 44.7/100 (E). API: GET nerq.ai/v1/preflight?target=Rami Levy
Kan jeg bruke Rami Levy i et regulert miljø?
Rami Levy: 44.7/100 (E). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Se også

Disclaimer: Nerqs tillitspoeng er automatiserte vurderinger basert på offentlig tilgjengelige signaler. De utgjør ikke anbefalinger eller garantier. Utfør alltid din egen verifisering.

Vi bruker informasjonskapsler for analyse og hurtiglagring. Personvern