Kv Memory est-il sûr ?

Kv Memory — Nerq Trust Score 60.0/100 (Note C). Score basé sur 5 independent trust signals.

Kv Memory est un software tool avec un Nerq Trust Score de 60.0/100 (C), basé sur 5 dimensions de données indépendantes. Sécurité: 0/100. Maintenance: 1/100. Popularité: 0/100. Données de plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard. Dernière mise à jour: n/a. Données lisibles par machine (JSON).

Kv Memory est-il sûr ?

Détail du score de confiance — Kv Memory has a Nerq Trust Score of 60.0/100 (C). Measured across 5 independent trust signals.

Analyse de Sécurité → Rapport de confidentialité de Kv Memory →

Quel est le score de confiance de Kv Memory ?

Kv Memory a un Score de Confiance Nerq de 60.0/100, obtenant la note C. Ce score est basé sur 5 dimensions mesurées indépendamment.

Sécurité
0
Conformité
100
Maintenance
1
Documentation
0
Popularité
0

Quels sont les résultats de sécurité clés pour Kv Memory ?

Le signal le plus fort de Kv Memory est conformité à 100/100. Aucune vulnérabilité connue n'a été détectée.

⚠Score de sécurité: 0/100 (faible)
⚠Maintenance: 1/100 — faible activité de maintenance
⚠Conformité: 100/100 — covers 52 of 52 jurisdictions
⚠Documentation: 0/100 — documentation limitée
⚠Popularité: 0/100 — 2 étoiles sur github

Qu'est-ce que Kv Memory et qui le maintient ?

Auteuraokihu
CatégorieInfrastructure
Étoiles2
Sourcehttps://github.com/aokihu/kv-memory
Protocolsmcp · rest

Conformité réglementaire

EU AI Act Risk ClassMINIMAL
Compliance Score100/100
JurisdictionsAssessed across 52 jurisdictions

Alternatives populaires dans infrastructure

n8n-io/n8n
69.1/100 · C
github
langflow-ai/langflow
77.0/100 · B
github
langgenius/dify
69.7/100 · C
github
open-webui/open-webui
60.4/100 · C
github
google-gemini/gemini-cli
56.2/100 · D
github

Kv Memory sur d'autres plateformes

Même développeur/entreprise dans d'autres registres :

mqtt-as-http
48/100 · npm
websocket-audio-api
48/100 · npm

What Is Kv Memory?

Kv Memory is a software tool in the infrastructure category: A key-value memory MCP tool with session management and SQLite storage.. It has 2 GitHub stars. Nerq Trust Score: 60/100 (C).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sécurité vulnerabilities, maintenance activity, license conformité, and adoption par la communauté.

How Nerq Assesses Kv Memory's Safety

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

The overall Trust Score of 60.0/100 (C) 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 Kv Memory?

Kv Memory is commonly evaluated by:

How to read the signals: Kv Memory's measured signals (sécurité 0/100, maintenance 1/100, documentation 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 Kv Memory's Safety Yourself

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

  1. Check the source code — Examiner le/la repository's sécurité 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 known vulnerabilities in Kv Memory's dependency tree.
  3. Avis permissions — Understand what access Kv Memory requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Kv Memory 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=kv-memory
  6. Examiner le/la license — Confirm that Kv Memory'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Kv Memory

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

Data handling

Understand how Kv Memory processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sécurité

Check Kv Memory's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.

Update frequency

Regularly check for updates to Kv Memory. Sécurité patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Kv Memory 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 conformité

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

Kv Memory and the EU AI Act

Kv Memory is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.

Nerq's conformité assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal conformité.

Best Practices for Using Kv Memory Safely

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

Conduct regular audits

Periodically review how Kv Memory is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.

Keep dependencies updated

Ensure Kv Memory and all its dependencies are running the latest stable versions to benefit from sécurité patches.

Follow least privilege

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

Monitor for sécurité advisories

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

Situations That Warrant Independent Review of Kv Memory

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

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

How Kv Memory Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average Trust Score is 62/100. Kv Memory's score of 60.0/100 is near the category average of 62/100.

This places Kv Memory in line with the typical infrastructure 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 modéré 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 Kv Memory 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 maintenance patterns change, Kv Memory'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 sécurité and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Kv Memory's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=kv-memory&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 — sécurité, maintenance, documentation, conformité, and community — has evolved independently, providing granular visibility into which aspects of Kv Memory are strengthening or weakening over time.

Kv Memory vs Alternatives

In the infrastructure category, Kv Memory scores 60.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Points Essentiels

Questions fréquentes

Kv Memory est-il sûr ?
kv-memory avec un Nerq Trust Score de 60.0/100 (C). Signal le plus fort : conformité (100/100). Score basé sur Sécurité (0/100), Maintenance (1/100), Popularité (0/100), Documentation (0/100).
Quel est le score de confiance de Kv Memory ?
kv-memory: 60.0/100 (C). Score basé sur Sécurité (0/100), Maintenance (1/100), Popularité (0/100), Documentation (0/100). Compliance: 100/100. Les scores sont mis à jour lorsque de nouvelles données sont disponibles. API: GET nerq.ai/v1/preflight?target=kv-memory
Quelles sont les alternatives plus sûres à Kv Memory ?
Dans la catégorie Infrastructure, higher-rated alternatives include n8n-io/n8n (69/100), langflow-ai/langflow (77/100), langgenius/dify (70/100). kv-memory scores 60.0/100.
À quelle fréquence le score de sécurité de Kv Memory est-il mis à jour ?
Nerq recomputes Kv Memory's trust score as new data becomes available. Current: 60.0/100 (C). API: GET nerq.ai/v1/preflight?target=kv-memory
Puis-je utiliser Kv Memory dans un environnement réglementé ?
Kv Memory: 60.0/100 (C). Compliance: 52 of 52 jurisdictions. EU AI Act compliant. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Voir aussi

Disclaimer: Les scores de confiance Nerq sont des évaluations automatisées basées sur des signaux publiquement disponibles. Ce ne sont pas des recommandations ou des garanties. Effectuez toujours votre propre vérification.

Nous utilisons des cookies pour l'analyse et le cache. Confidentialité