Code Archeologist est-il sûr ?
Code Archeologist — Nerq Trust Score 63.0/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-02.
Utilisez Code Archeologist avec précaution. Code Archeologist is a software tool avec un Score de Confiance Nerq de 63.0/100 (C), based on 5 dimensions de données indépendantes. It is below the recommended threshold of 70. Sécurité: 0/100. Maintenance: 1/100. Popularity: 0/100. Données provenant de multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Dernière mise à jour: 2026-04-02. Données lisibles par machine (JSON).
Code Archeologist est-il sûr ?
CAUTION — Code Archeologist a un Score de Confiance Nerq de 63.0/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.
Quel est le score de confiance de Code Archeologist ?
Code Archeologist a un Score de Confiance Nerq de 63.0/100, obtenant la note C. Ce score est basé sur 5 dimensions mesurées indépendamment.
Quels sont les résultats de sécurité clés pour Code Archeologist ?
Le signal le plus fort de Code Archeologist est conformité à 100/100. Aucune vulnérabilité connue n'a été détectée. N'a pas encore atteint le seuil vérifié Nerq de 70+.
Qu'est-ce que Code Archeologist et qui le maintient ?
| Auteur | veerakarthick235 |
| Catégorie | coding |
| Source | https://github.com/veerakarthick235/Code-Archeologist |
| Protocols | rest |
Conformité réglementaire
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Alternatives populaires dans coding
What Is Code Archeologist?
Code Archeologist is a software tool in the coding category: An advanced multi-agent system that automates the migration of legacy codebases to modern stacks using Gemini 3.0.. Nerq Trust Score: 63/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 Code Archeologist's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Code Archeologist performs in each:
- Sécurité (0/100): Code Archeologist's sécurité posture is poor. This score factors in known CVEs, dependency vulnerabilities, sécurité policy presence, and code signing practices.
- Maintenance (1/100): Code Archeologist is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
- Compliance (100/100): Code Archeologist is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Basé sur GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 63.0/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 Code Archeologist?
Code Archeologist 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: Code Archeologist 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 Code Archeologist's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Examiner le/la repository's sécurité policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Code Archeologist's dependency tree. - Avis permissions — Understand what access Code Archeologist requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Code Archeologist 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=Code-Archeologist - Examiner le/la license — Confirm that Code Archeologist'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Code Archeologist
When evaluating whether Code Archeologist is safe, consider these category-specific risks:
Understand how Code Archeologist processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Code Archeologist's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.
Regularly check for updates to Code Archeologist. Sécurité patches and bug fixes are only effective if you're running the latest version.
If Code Archeologist 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 Code Archeologist's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Code Archeologist in violation of its license can expose your organization to legal liability.
Code Archeologist and the EU AI Act
Code Archeologist 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 Code Archeologist Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Code Archeologist while minimizing risk:
Periodically review how Code Archeologist is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.
Ensure Code Archeologist and all its dependencies are running the latest stable versions to benefit from sécurité patches.
Grant Code Archeologist only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Code Archeologist's sécurité advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Code Archeologist is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Code Archeologist?
Even promising tools aren't right for every situation. Consider avoiding Code Archeologist in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional conformité review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Code Archeologist de 63.0/100 meets your organization's risk tolerance. We recommend running a manual sécurité assessment alongside the automated Nerq score.
How Code Archeologist Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Trust Score is 62/100. Code Archeologist's score of 63.0/100 is above the category average of 62/100.
This positions Code Archeologist favorably among coding 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 Code Archeologist 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, Code Archeologist'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 Code Archeologist's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Code-Archeologist&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 Code Archeologist are strengthening or weakening over time.
Code Archeologist vs Alternatives
In the coding category, Code Archeologist scores 63.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Code Archeologist vs AutoGPT — Trust Score: 74.7/100
- Code Archeologist vs ollama — Trust Score: 73.8/100
- Code Archeologist vs langchain — Trust Score: 86.4/100
Points Essentiels
- Code Archeologist a un Score de Confiance de 63.0/100 (C) and is not yet Nerq Verified.
- Code Archeologist shows modéré trust signals. Conduct thorough due diligence before deploying to production environments.
- Among coding tools, Code Archeologist scores above the category average of 62/100, demonstrating above-average reliability.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Questions fréquentes
Est-ce que Code Archeologist sûr à utiliser?
Qu'est-ce que Code Archeologist's trust score ?
Quelles sont les alternatives plus sûres à Code Archeologist ?
How often is Code Archeologist's safety score updated?
Can I use Code Archeologist in a regulated environment?
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.