Er Agentic 641Ea102 sikker?
Agentic 641Ea102 — Nerq Trust Score 62.9/100 (Karakter C). Baseret på analyse af 5 tillidsdimensioner vurderes det som generelt sikkert men med visse bekymringer. Sidst opdateret: 2026-07-16.
Brug Agentic 641Ea102 med forsigtighed. Agentic 641Ea102 er en software tool med en Nerq Tillidsscore på 62.9/100 (C), based on 5 uafhængige datadimensioner. Under Nerqs verificerede tærskel Sikkerhed: 0/100. Vedligeholdelse: 1/100. Popularitet: 0/100. Data hentet fra flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sidst opdateret: 2026-07-16. Maskinlæsbare data (JSON).
Er Agentic 641Ea102 sikker?
CAUTION — Agentic 641Ea102 has a Nerq Trust Score of 62.9/100 (C). Har moderat tillidssignaler, men viser nogle bekymrende områder that warrant attention. Suitable for development use — review sikkerhed and vedligeholdelse signals before production deployment.
Hvad er Agentic 641Ea102s tillidsscore?
Agentic 641Ea102 har en Nerq Trust Score på 62.9/100 med karakteren C. Denne score er baseret på 5 uafhængigt målte dimensioner, herunder sikkerhed, vedligeholdelse og community-adoption.
Hvad er de vigtigste sikkerhedsresultater for Agentic 641Ea102?
Agentic 641Ea102s stærkeste signal er overholdelse på 100/100. Ingen kendte sårbarheder er fundet. It has not yet reached the Nerq Verified threshold of 70+.
Hvad er Agentic 641Ea102 og hvem vedligeholder det?
| Udvikler | Design-Arena-Gens |
| Kategori | Coding |
| Kilde | https://github.com/Design-Arena-Gens/agentic-641ea102 |
| Frameworks | autogen |
| Protocols | rest |
Lovgivningsmæssig overholdelse
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Populære alternativer i coding
What Is Agentic 641Ea102?
Agentic 641Ea102 is a software tool in the coding category: AI-generated project created by Agentic CLI.. Nerq Trust Score: 63/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhed vulnerabilities, vedligeholdelse activity, license overholdelse, and fællesskabsadoption.
How Nerq Assesses Agentic 641Ea102's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensioner. Here is how Agentic 641Ea102 performs in each:
- Sikkerhed (0/100): Agentic 641Ea102's sikkerhed posture is poor. This score factors in known CVEs, dependency vulnerabilities, sikkerhed policy presence, and code signing practices.
- Vedligeholdelse (1/100): Agentic 641Ea102 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 dokumentation, usage examples, and contribution guidelines.
- Compliance (100/100): Agentic 641Ea102 is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Baseret på GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 62.9/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 Agentic 641Ea102?
Agentic 641Ea102 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: Agentic 641Ea102 is suitable for development and testing environments. Before production deployment, conduct a thorough review of its sikkerhed posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.
How to Verify Agentic 641Ea102's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Gennemgå repository's sikkerhed policy, open issues, and recent commits for signs of active vedligeholdelse.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Agentic 641Ea102's dependency tree. - Anmeldelse permissions — Understand what access Agentic 641Ea102 requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Agentic 641Ea102 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=agentic-641ea102 - Gennemgå license — Confirm that Agentic 641Ea102'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 sikkerhed concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Agentic 641Ea102
When evaluating whether Agentic 641Ea102 is safe, consider these category-specific risks:
Understand how Agentic 641Ea102 processes, stores, and transmits your data. Gennemgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Agentic 641Ea102's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sikkerhed risk.
Regularly check for updates to Agentic 641Ea102. Sikkerhed patches and bug fixes are only effective if you're running the latest version.
If Agentic 641Ea102 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 Agentic 641Ea102's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Agentic 641Ea102 in violation of its license can expose your organization to legal liability.
Agentic 641Ea102 and the EU AI Act
Agentic 641Ea102 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 overholdelse assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal overholdelse.
Best Practices for Using Agentic 641Ea102 Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Agentic 641Ea102 while minimizing risk:
Periodically review how Agentic 641Ea102 is used in your workflow. Check for unexpected behavior, permissions drift, and overholdelse with your sikkerhed policies.
Ensure Agentic 641Ea102 and all its dependencies are running the latest stable versions to benefit from sikkerhed patches.
Grant Agentic 641Ea102 only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Agentic 641Ea102's sikkerhed advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Agentic 641Ea102 is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Agentic 641Ea102?
Even promising tools aren't right for every situation. Consider avoiding Agentic 641Ea102 in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional overholdelse review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Agentic 641Ea102's trust score of 62.9/100 meets your organization's risk tolerance. We recommend running a manual sikkerhed assessment alongside the automated Nerq score.
How Agentic 641Ea102 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. Agentic 641Ea102's score of 62.9/100 is above the category average of 62/100.
This positions Agentic 641Ea102 favorably among coding tools. While it outperforms the average, there is still room for improvement in certain trust dimensioner.
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 Agentic 641Ea102 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 vedligeholdelse patterns change, Agentic 641Ea102'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 sikkerhed and quality. Conversely, a downward trend may signal reduced vedligeholdelse, growing technical debt, or unresolved vulnerabilities. To track Agentic 641Ea102's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=agentic-641ea102&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 — sikkerhed, vedligeholdelse, dokumentation, overholdelse, and community — has evolved independently, providing granular visibility into which aspects of Agentic 641Ea102 are strengthening or weakening over time.
Agentic 641Ea102 vs Alternativer
In the coding category, Agentic 641Ea102 scores 62.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Agentic 641Ea102 vs AutoGPT — Trust Score: 61.8/100
- Agentic 641Ea102 vs ollama — Trust Score: 56.5/100
- Agentic 641Ea102 vs langchain — Trust Score: 69.8/100
Vigtigste pointer
- Agentic 641Ea102 has a Trust Score of 62.9/100 (C) and is not yet Nerq Verified.
- Agentic 641Ea102 shows moderat trust signals. Conduct thorough due diligence before deploying to production environments.
- Among coding tools, Agentic 641Ea102 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.
Ofte stillede spørgsmål
Er Agentic 641Ea102 sikker?
Hvad er Agentic 641Ea102s tillidsscore?
Hvad er sikrere alternativer til Agentic 641Ea102?
Hvor ofte opdateres Agentic 641Ea102s sikkerhedsscore?
Kan jeg bruge Agentic 641Ea102 i et reguleret miljø?
Se også
Disclaimer: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.