Cursor Usage est-il sûr ?

Cursor Usage — Nerq Trust Score 55.0/100 (Note D). Sur la base de l'analyse de 5 dimensions de confiance, il est a des préoccupations de sécurité notables. Dernière mise à jour : 2026-04-05.

Utilisez Cursor Usage avec précaution. Cursor Usage est un software tool avec un Nerq Trust Score de 55.0/100 (D), 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-05. Données lisibles par machine (JSON).

Cursor Usage est-il sûr ?

CAUTION — Cursor Usage has a Nerq Trust Score of 55.0/100 (D). 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 Cursor Usage →

Quel est le score de confiance de Cursor Usage ?

Cursor Usage a un Score de Confiance Nerq de 55.0/100, obtenant la note D. Ce score est basé sur 5 dimensions mesurées indépendamment.

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

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

Le signal le plus fort de Cursor Usage est conformité à 70/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é: 70/100 — covers 36 of 52 jurisdictions
Documentation: 0/100 — documentation limitée
Popularité: 0/100 — adoption communautaire

Qu'est-ce que Cursor Usage et qui le maintient ?

Auteurofershap
CatégorieFinance
Sourcehttps://github.com/ofershap/cursor-usage
Protocolsmcp

Conformité réglementaire

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

Alternatives populaires dans finance

OpenBB-finance/OpenBB
78.7/100 · B
github
microsoft/qlib
91.2/100 · A+
github
TauricResearch/TradingAgents
87.9/100 · A
github
TradingAgents-CN
80.7/100 · A
github
virattt/dexter
73.3/100 · B
github

Cursor Usage sur d'autres plateformes

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

cursor-usage-tracker
67/100 · npm
ai-context-kit
60/100 · npm
spotlight-card
60/100 · npm
hover-effects-canvas
60/100 · npm
tiny-pmap
60/100 · npm

What Is Cursor Usage?

Cursor Usage is a software tool in the finance category: Ask your AI agent about Cursor spending.. Nerq Trust Score: 55/100 (D).

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 Cursor Usage's Safety

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

The overall Trust Score of 55.0/100 (D) 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 Cursor Usage?

Cursor Usage is designed for:

Risk guidance: Cursor Usage 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 Cursor Usage'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é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 Cursor Usage's dependency tree.
  3. Avis permissions — Understand what access Cursor Usage requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Cursor Usage 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=cursor-usage
  6. Examiner le/la license — Confirm that Cursor Usage'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 Cursor Usage

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

Data handling

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

Third-party integrations

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

Cursor Usage and the EU AI Act

Cursor Usage 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 Cursor Usage Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for sécurité advisories

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

When Should You Avoid Cursor Usage?

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

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

How Cursor Usage Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among finance tools, the average Trust Score is 62/100. Cursor Usage's score of 55.0/100 is near the category average of 62/100.

This places Cursor Usage in line with the typical finance 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 Cursor Usage 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, Cursor Usage'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 Cursor Usage's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=cursor-usage&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 Cursor Usage are strengthening or weakening over time.

Cursor Usage vs Alternatives

In the finance category, Cursor Usage scores 55.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Points Essentiels

Questions fréquentes

Cursor Usage est-il sûr ?
Utiliser avec prudence. cursor-usage avec un Nerq Trust Score de 55.0/100 (D). Signal le plus fort : conformité (70/100). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100).
Quel est le score de confiance de Cursor Usage ?
cursor-usage: 55.0/100 (D). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100). Compliance: 70/100. Les scores sont mis à jour lorsque de nouvelles données sont disponibles. API: GET nerq.ai/v1/preflight?target=cursor-usage
Quelles sont les alternatives plus sûres à Cursor Usage ?
Dans la catégorie Finance, higher-rated alternatives include OpenBB-finance/OpenBB (79/100), microsoft/qlib (91/100), TauricResearch/TradingAgents (88/100). cursor-usage scores 55.0/100.
À quelle fréquence le score de sécurité de Cursor Usage est-il mis à jour ?
Nerq continuously monitors Cursor Usage and updates its trust score as new data becomes available. Données provenant de plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard. Current: 55.0/100 (D), last vérifié 2026-04-05. API: GET nerq.ai/v1/preflight?target=cursor-usage
Puis-je utiliser Cursor Usage dans un environnement réglementé ?
Cursor Usage has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
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é