Is Codex Keeper veilig?
Codex Keeper — Nerq Vertrouwensscore 46.5/100 (D-beoordeling). Op basis van analyse van 3 vertrouwensdimensies wordt het beschouwd als heeft opmerkelijke beveiligingszorgen. Laatst bijgewerkt: 2026-04-03.
Wees voorzichtig met Codex Keeper. Codex Keeper is een software tool met een Nerq Vertrouwensscore van 46.5/100 (D), based on 3 onafhankelijke gegevensdimensies. Het ligt onder de aanbevolen drempel van 70. Onderhoud: 0/100. Populariteit: 0/100. Gegevens afkomstig van multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Laatst bijgewerkt: 2026-04-03. Machineleesbare gegevens (JSON).
Is Codex Keeper veilig?
NEE — GEBRUIK MET VOORZICHTIGHEID — Codex Keeper heeft een Nerq Vertrouwensscore van 46.5/100 (D). Het heeft benedengemiddelde vertrouwenssignalen met aanzienlijke lacunes in beveiliging, onderhoud of documentatie. Niet aanbevolen voor productiegebruik zonder grondige handmatige controle en aanvullende beveiligingsmaatregelen.
Wat is de vertrouwensscore van Codex Keeper?
Codex Keeper heeft een Nerq Vertrouwensscore van 46.5/100 met het cijfer D. Deze score is gebaseerd op 3 onafhankelijk gemeten dimensies, waaronder beveiliging, onderhoud en community-adoptie.
Wat zijn de belangrijkste beveiligingsbevindingen voor Codex Keeper?
Het sterkste signaal van Codex Keeper is onderhoud met 0/100. Er zijn geen bekende kwetsbaarheden gedetecteerd. It has not yet reached the Nerq Verified threshold of 70+.
Wat is Codex Keeper en wie onderhoudt het?
| Ontwikkelaar | https://github.com/aindreyway/mcp-codex-keeper |
| Categorie | coding |
| Sterren | 75 |
| Bron | https://github.com/aindreyway/mcp-codex-keeper |
Populaire alternatieven in coding
What Is Codex Keeper?
Codex Keeper is a software tool in the coding category: Provides curated development knowledge for code generation, bug fixing, and context-aware programming advice.. It has 75 GitHub stars. Nerq Vertrouwensscore: 46/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.
How Nerq Assesses Codex Keeper's Safety
Nerq's Vertrouwensscore is calculated from 13+ independent signals aggregated into five dimensies. Here is how Codex Keeper performs in each:
- Onderhoud (0/100): Codex Keeper is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API documentatie, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Gebaseerd op GitHub stars, forks, download counts, and ecosystem integrations.
The overall Vertrouwensscore of 46.5/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 Codex Keeper?
Codex Keeper is designed for:
- Developers and teams working with coding tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Codex Keeper. The low trust score suggests potential risks in beveiliging, onderhoud, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Codex Keeper's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Bekijk de repository beveiliging policy, open issues, and recent commits for signs of active onderhoud.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for bekende kwetsbaarheden in Codex Keeper's dependency tree. - Beoordeling permissions — Understand what access Codex Keeper requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Codex Keeper in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=Codex Keeper - Bekijk de license — Confirm that Codex Keeper'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.
- 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 beveiliging concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Codex Keeper
When evaluating whether Codex Keeper is safe, consider these category-specific risks:
Understand how Codex Keeper processes, stores, and transmits your data. Bekijk de tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Codex Keeper's dependency tree for bekende kwetsbaarheden. Tools with outdated or unmaintained dependencies pose a higher beveiliging risk.
Regularly check for updates to Codex Keeper. Beveiliging patches and bug fixes are only effective if you're running the latest version.
If Codex Keeper 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.
Verify that Codex Keeper's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Codex Keeper in violation of its license can expose your organization to legal liability.
Best Practices for Using Codex Keeper Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Codex Keeper while minimizing risk:
Periodically review how Codex Keeper is used in your workflow. Check for unexpected behavior, permissions drift, and naleving with your beveiliging policies.
Ensure Codex Keeper and all its dependencies are running the latest stable versions to benefit from beveiliging patches.
Grant Codex Keeper only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Codex Keeper's beveiliging advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Codex Keeper is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Codex Keeper?
Even promising tools aren't right for every situation. Consider avoiding Codex Keeper in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional naleving review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Codex Keeper is 46.5/100 meets your organization's risk tolerance. We recommend running a manual beveiliging assessment alongside the automated Nerq score.
How Codex Keeper Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Vertrouwensscore is 62/100. Codex Keeper's score of 46.5/100 is below the category average of 62/100.
This suggests that Codex Keeper trails behind many comparable coding tools. Organizations with strict beveiliging 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 matig 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.
Vertrouwensscore History
Nerq continuously monitors Codex Keeper and recalculates its Vertrouwensscore 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 onderhoud patterns change, Codex Keeper'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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, growing technical debt, or unresolved vulnerabilities. To track Codex Keeper's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Codex Keeper&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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Codex Keeper are strengthening or weakening over time.
Codex Keeper vs Alternatieven
In the coding category, Codex Keeper scores 46.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Codex Keeper vs AutoGPT — Vertrouwensscore: 74.7/100
- Codex Keeper vs ollama — Vertrouwensscore: 73.8/100
- Codex Keeper vs langchain — Vertrouwensscore: 86.4/100
Belangrijkste conclusies
- Codex Keeper has a Vertrouwensscore of 46.5/100 (D) and is not yet Nerq Verified.
- Codex Keeper has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among coding tools, Codex Keeper scores below the category average of 62/100, suggesting room for improvement relative to peers.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Veelgestelde vragen
Is Codex Keeper veilig om te gebruiken?
Wat is Codex Keeper's trust score?
Wat zijn veiligere alternatieven voor Codex Keeper?
How often is Codex Keeper's safety score updated?
Kan ik Codex Keeper gebruiken in een gereguleerde omgeving?
Disclaimer: Nerq-vertrouwensscores zijn geautomatiseerde beoordelingen op basis van openbaar beschikbare signalen. Ze vormen geen aanbeveling of garantie. Voer altijd uw eigen verificatie uit.