Ist Codify Mcp sicher?

Codify Mcp — Nerq Trust Score 54.7/100 (Note D). Basierend auf der Analyse von 1 Vertrauensdimensionen wird es als bemerkenswerte Sicherheitsbedenken eingestuft. Zuletzt aktualisiert: 2026-04-06.

Verwende Codify Mcp mit Vorsicht. Codify Mcp ist ein software tool mit einem Nerq-Vertrauenswert von 54.7/100 (D), basierend auf 3 unabhängigen Datendimensionen. Unter der Nerq-Vertrauensschwelle Daten von mehreren öffentlichen Quellen einschließlich Paketregistern, GitHub, NVD, OSV.dev und OpenSSF Scorecard. Zuletzt aktualisiert: 2026-04-06. Maschinenlesbare Daten (JSON).

Ist Codify Mcp sicher?

CAUTION — Codify Mcp has a Nerq Trust Score of 54.7/100 (D). Es hat moderat Vertrauenssignale, zeigt aber einige Problembereiche that warrant attention. Suitable for development use — review Sicherheit and Wartung signals before production deployment.

Sicherheitsanalyse → Codify Mcp Datenschutzbericht →

Was ist die Vertrauensbewertung von Codify Mcp?

Codify Mcp hat eine Nerq-Vertrauensbewertung von 54.7/100 und erhält die Note D. Diese Bewertung basiert auf 1 unabhängig gemessenen Dimensionen.

Konformität
100

Was sind die wichtigsten Sicherheitsergebnisse für Codify Mcp?

Das stärkste Signal von Codify Mcp ist konformität mit 100/100. Es wurden keine bekannten Schwachstellen erkannt. Hat die Nerq-Vertrauensschwelle von 70+ noch nicht erreicht.

Konformität: 100/100 — covers 52 of 52 jurisdictions

Was ist Codify Mcp und wer pflegt es?

Autorcyberfly
KategorieUncategorized
Quellehttps://www.npmjs.com/package/codify-mcp

Regulatorische Konformität

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

Codify Mcp auf anderen Plattformen

Gleicher Entwickler/Unternehmen in anderen Registern:

cyber-comms
48/100 · npm
cyber-human
48/100 · npm

What Is Codify Mcp?

Codify Mcp is a software tool in the uncategorized category: MCP server for custom automation tools using Apify Agent. Easily create reusable automations from casual browser actions.. Nerq Trust Score: 55/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including Sicherheit vulnerabilities, Wartung activity, license Konformität, and Community-Akzeptanz.

How Nerq Assesses Codify Mcp's Safety

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

The overall Trust Score of 54.7/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 Codify Mcp?

Codify Mcp is designed for:

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

How to Verify Codify Mcp's Safety Yourself

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

  1. Check the source code — Überprüfen Sie das/die repository Sicherheit policy, open issues, and recent commits for signs of active Wartung.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Codify Mcp's dependency tree.
  3. Bewertung permissions — Understand what access Codify Mcp requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Codify Mcp 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=codify-mcp
  6. Überprüfen Sie das/die license — Confirm that Codify Mcp'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 Sicherheit concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Codify Mcp

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

Data handling

Understand how Codify Mcp processes, stores, and transmits your data. Überprüfen Sie das/die tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency Sicherheit

Check Codify Mcp's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher Sicherheit risk.

Update frequency

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

Third-party integrations

If Codify Mcp 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 Konformität

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

Best Practices for Using Codify Mcp Safely

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

Conduct regular audits

Periodically review how Codify Mcp is used in your workflow. Check for unexpected behavior, permissions drift, and Konformität with your Sicherheit policies.

Keep dependencies updated

Ensure Codify Mcp and all its dependencies are running the latest stable versions to benefit from Sicherheit patches.

Follow least privilege

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

Monitor for Sicherheit advisories

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

When Should You Avoid Codify Mcp?

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

For each scenario, evaluate whether Codify Mcp's trust score of 54.7/100 meets your organization's risk tolerance. We recommend running a manual Sicherheit assessment alongside the automated Nerq score.

How Codify Mcp 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. Codify Mcp's score of 54.7/100 is near the category average of 62/100.

This places Codify Mcp in line with the typical uncategorized 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 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 Codify Mcp 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 Wartung patterns change, Codify Mcp'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 Sicherheit and quality. Conversely, a downward trend may signal reduced Wartung, growing technical debt, or unresolved vulnerabilities. To track Codify Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=codify-mcp&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 — Sicherheit, Wartung, Dokumentation, Konformität, and community — has evolved independently, providing granular visibility into which aspects of Codify Mcp are strengthening or weakening over time.

Wichtigste Punkte

Häufig gestellte Fragen

Ist Codify Mcp sicher?
Mit Vorsicht verwenden. codify-mcp mit einem Nerq-Vertrauenswert von 54.7/100 (D). Stärkstes Signal: konformität (100/100). Bewertung basierend auf multiple trust Dimensionen.
Was ist die Vertrauensbewertung von Codify Mcp?
codify-mcp: 54.7/100 (D). Bewertung basierend auf multiple trust Dimensionen. Compliance: 100/100. Bewertungen werden aktualisiert, wenn neue Daten verfügbar werden. API: GET nerq.ai/v1/preflight?target=codify-mcp
Was sind sicherere Alternativen zu Codify Mcp?
In der Kategorie Uncategorized, more software tools are being analyzed — schauen Sie bald wieder vorbei. codify-mcp scores 54.7/100.
Wie oft wird die Sicherheitsbewertung von Codify Mcp aktualisiert?
Nerq continuously monitors Codify Mcp and updates its trust score as new data becomes available. Daten stammen von mehreren öffentlichen Quellen einschließlich Paketregistern, GitHub, NVD, OSV.dev und OpenSSF Scorecard. Current: 54.7/100 (D), last verifiziert 2026-04-06. API: GET nerq.ai/v1/preflight?target=codify-mcp
Kann ich Codify Mcp in einer regulierten Umgebung verwenden?
Codify Mcp has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Siehe auch

Disclaimer: Nerq-Vertrauensbewertungen sind automatisierte Bewertungen basierend auf öffentlich verfügbaren Signalen. Sie sind keine Empfehlungen oder Garantien. Führen Sie immer Ihre eigene Sorgfaltsprüfung durch.

Wir verwenden Cookies für Analysen und Caching. Datenschutz