Raphtory est-il sûr ?

Raphtory — Nerq Trust Score 68.6/100 (Note C). Sur la base de l'analyse de 5 dimensions de confiance, il est généralement sûr mais avec quelques préoccupations. Dernière mise à jour : 2026-04-24.

Utilisez Raphtory avec précaution. Raphtory est un software tool avec un Nerq Trust Score de 68.6/100 (C), basé sur 5 dimensions de données indépendantes. En dessous du seuil vérifié Nerq Sécurité: 0/100. Maintenance: 0/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: 2026-04-24. Données lisibles par machine (JSON).

Raphtory est-il sûr ?

CAUTION — Raphtory has a Nerq Trust Score of 68.6/100 (C). Il présente des signaux de confiance modérés mais montre certaines zones de préoccupation that warrant attention. Suitable for development use — review sécurité and maintenance signals before production deployment.

Analyse de Sécurité → Rapport de confidentialité de Raphtory →

Quel est le score de confiance de Raphtory ?

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

Sécurité
0
Conformité
80
Maintenance
0
Documentation
0
Popularité
0

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

Le signal le plus fort de Raphtory est conformité à 80/100. Aucune vulnérabilité connue n'a été détectée. N'a pas encore atteint le seuil vérifié Nerq de 70+.

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

Qu'est-ce que Raphtory et qui le maintient ?

AuteurUnknown
CatégorieUncategorized
Étoiles569
Sourcehttps://github.com/Pometry/Raphtory

Conformité réglementaire

EU AI Act Risk ClassNot assessed
Compliance Score80/100
JurisdictionsAssessed across 52 jurisdictions

What Is Raphtory?

Raphtory is a software tool in the uncategorized category: Scalable graph analytics database powered by a multithreaded, vectorized temporal engine, written in Rust. It has 569 GitHub stars. Nerq Trust Score: 69/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 Raphtory's Safety

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

The overall Trust Score of 68.6/100 (C) 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 Raphtory?

Raphtory is designed for:

Risk guidance: Raphtory is suitable for development and testing environments. Before production deployment, conduct a thorough review of its sécurité posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify Raphtory'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 Raphtory's dependency tree.
  3. Avis permissions — Understand what access Raphtory requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Raphtory 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=Pometry/Raphtory
  6. Examiner le/la license — Confirm that Raphtory'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 Raphtory

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

Data handling

Understand how Raphtory 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 Raphtory'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 Raphtory. Sécurité patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Raphtory 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 Raphtory's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Raphtory in violation of its license can expose your organization to legal liability.

Best Practices for Using Raphtory Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for sécurité advisories

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

When Should You Avoid Raphtory?

Even promising tools aren't right for every situation. Consider avoiding Raphtory in these scenarios:

For each scenario, evaluate whether Raphtory's trust score of 68.6/100 meets your organization's risk tolerance. We recommend running a manual sécurité assessment alongside the automated Nerq score.

How Raphtory Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Raphtory's score of 68.6/100 is above the category average of 62/100.

This positions Raphtory favorably among uncategorized tools. While it outperforms the average, there is still room for improvement in certain trust dimensions.

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 Raphtory 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, Raphtory'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 Raphtory's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Pometry/Raphtory&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 Raphtory are strengthening or weakening over time.

Points Essentiels

Analyse détaillée du score

DimensionScore
Sécurité0/100
Maintenance0/100
Popularité0/100

Basé sur 3 dimensions. Data from plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard.

Quelles données Raphtory collecte-t-il ?

Confidentialité assessment for Raphtory is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.

Raphtory est-il sécurisé ?

Sécurité score: 0/100. Review sécurité practices and consider alternatives with higher sécurité scores for sensitive use cases.

Nerq surveille cette entité par rapport à NVD, OSV.dev et aux bases de données de vulnérabilités spécifiques aux registres pour une évaluation de sécurité continue.

Analyse complète : Rapport de sécurité de Raphtory

Comment nous avons calculé ce score

Raphtory's trust score of 68.6/100 (C) est calculé à partir de plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard. Le score reflète 3 dimensions indépendantes: sécurité (0/100), maintenance (0/100), popularité (0/100). Chaque dimension est pondérée de manière égale pour produire le score de confiance composite.

Nerq analyse plus de 7,5 millions d'entités dans 26 registres en utilisant la même méthodologie, permettant une comparaison directe entre entités. Les scores sont mis à jour en continu dès que de nouvelles données sont disponibles.

Cette page a été révisée pour la dernière fois le April 24, 2026. Version des données: 1.0.

Documentation complète de la méthodologie · Données lisibles par machine (API JSON)

Questions fréquentes

Raphtory est-il sûr ?
Utiliser avec prudence. Pometry/Raphtory avec un Nerq Trust Score de 68.6/100 (C). Signal le plus fort : conformité (80/100). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100).
Quel est le score de confiance de Raphtory ?
Pometry/Raphtory: 68.6/100 (C). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100). Compliance: 80/100. Les scores sont mis à jour lorsque de nouvelles données sont disponibles. API: GET nerq.ai/v1/preflight?target=Pometry/Raphtory
Quelles sont les alternatives plus sûres à Raphtory ?
Dans la catégorie Uncategorized, d'autres software tool sont en cours d'analyse — revenez bientôt. Pometry/Raphtory scores 68.6/100.
À quelle fréquence le score de sécurité de Raphtory est-il mis à jour ?
Nerq continuously monitors Raphtory and updates its trust score as new data becomes available. Current: 68.6/100 (C), last vérifié 2026-04-24. API: GET nerq.ai/v1/preflight?target=Pometry/Raphtory
Puis-je utiliser Raphtory dans un environnement réglementé ?
Raphtory n'a pas atteint le seuil de vérification Nerq de 70. Vérification supplémentaire recommandée.
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é