Builder Agent è sicuro?

Builder Agent — Nerq Trust Score 53.6/100 (Grado D). Sulla base dell'analisi di 1 dimensioni di fiducia, è ha preoccupazioni di sicurezza notevoli. Ultimo aggiornamento: 2026-04-27.

Usa Builder Agent con cautela. Builder Agent è un software tool con un Punteggio di fiducia Nerq di 53.6/100 (D), based on 3 dimensioni di dati indipendenti. Sotto la soglia verificata Nerq Dati provenienti da molteplici fonti pubbliche tra cui registri di pacchetti, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Ultimo aggiornamento: 2026-04-27. Dati leggibili dalle macchine (JSON).

Builder Agent è sicuro?

CAUTION — Builder Agent has a Nerq Trust Score of 53.6/100 (D). Ha segnali di fiducia moderati ma mostra alcune aree di preoccupazione that warrant attention. Suitable for development use — review sicurezza and manutenzione signals before production deployment.

Analisi di Sicurezza → Report sulla privacy di Builder Agent →

Qual è il punteggio di fiducia di Builder Agent?

Builder Agent ha un Nerq Trust Score di 53.6/100 con voto D. Questo punteggio si basa su 1 dimensioni misurate indipendentemente, tra cui sicurezza, manutenzione e adozione della community.

Conformità
100

Quali sono i risultati di sicurezza chiave per Builder Agent?

Il segnale più forte di Builder Agent è conformità a 100/100. Non sono state rilevate vulnerabilità note. It has not yet reached the Nerq Verified threshold of 70+.

Conformità: 100/100 — covers 52 of 52 jurisdictions

Cos'è Builder Agent e chi lo mantiene?

Autorekermit247
CategoriaUncategorized
Fontehttps://www.npmjs.com/package/@gicm/builder-agent

Conformità normativa

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

Builder Agent su altre piattaforme

Stesso sviluppatore/azienda in altri registri:

@gicm/defi-agent
48/100 · npm
@gicm/growth-engine
48/100 · npm
@gicm/integration-hub
48/100 · npm
@gicm/activity-logger
48/100 · npm

What Is Builder Agent?

Builder Agent is a software tool in the uncategorized category: Code generation agent for gICM - builds integrations from approved discoveries. Nerq Trust Score: 54/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sicurezza vulnerabilities, manutenzione activity, license conformità, and adozione della comunità.

How Nerq Assesses Builder Agent's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensioni. Here is how Builder Agent performs in each:

The overall Trust Score of 53.6/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 Builder Agent?

Builder Agent is designed for:

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

How to Verify Builder Agent's Safety Yourself

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

  1. Check the source code — Controlla repository sicurezza policy, open issues, and recent commits for signs of active manutenzione.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Builder Agent's dependency tree.
  3. Recensione permissions — Understand what access Builder Agent requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Builder Agent 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=@gicm/builder-agent
  6. Controlla license — Confirm that Builder Agent'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 sicurezza concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Builder Agent

When evaluating whether Builder Agent is safe, consider these category-specific risks:

Data handling

Understand how Builder Agent processes, stores, and transmits your data. Controlla tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sicurezza

Check Builder Agent's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sicurezza risk.

Update frequency

Regularly check for updates to Builder Agent. Sicurezza patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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

Best Practices for Using Builder Agent Safely

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

Conduct regular audits

Periodically review how Builder Agent is used in your workflow. Check for unexpected behavior, permissions drift, and conformità with your sicurezza policies.

Keep dependencies updated

Ensure Builder Agent and all its dependencies are running the latest stable versions to benefit from sicurezza patches.

Follow least privilege

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

Monitor for sicurezza advisories

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

When Should You Avoid Builder Agent?

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

For each scenario, evaluate whether Builder Agent's trust score of 53.6/100 meets your organization's risk tolerance. We recommend running a manual sicurezza assessment alongside the automated Nerq score.

How Builder Agent 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. Builder Agent's score of 53.6/100 is near the category average of 62/100.

This places Builder Agent 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 moderato 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 Builder Agent 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 manutenzione patterns change, Builder Agent'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 sicurezza and quality. Conversely, a downward trend may signal reduced manutenzione, growing technical debt, or unresolved vulnerabilities. To track Builder Agent's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=@gicm/builder-agent&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 — sicurezza, manutenzione, documentazione, conformità, and community — has evolved independently, providing granular visibility into which aspects of Builder Agent are strengthening or weakening over time.

Punti chiave

Quali dati raccoglie Builder Agent?

Privacy assessment for Builder Agent is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.

Builder Agent è sicuro?

Sicurezza score: in fase di valutazione. Review sicurezza practices and consider alternatives with higher sicurezza scores for sensitive use cases.

Nerq monitora questa entità rispetto a NVD, OSV.dev e database di vulnerabilità specifici del registro per la valutazione continua della sicurezza.

Analisi completa: Report di sicurezza di Builder Agent

Builder Agent su altre piattaforme

Stesso sviluppatore/azienda in altri registri:

@gicm/defi-agent (npm, 48/100)@gicm/growth-engine (npm, 48/100)@gicm/integration-hub (npm, 48/100)@gicm/activity-logger (npm, 48/100)

Come abbiamo calcolato questo punteggio

Builder Agent's trust score of 53.6/100 (D) è calcolato da molteplici fonti pubbliche tra cui registri di pacchetti, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Il punteggio riflette 0 dimensioni indipendenti: . Ogni dimensione ha lo stesso peso per produrre il punteggio di fiducia complessivo.

Nerq analizza oltre 7,5 milioni di entità in 26 registri utilizzando la stessa metodologia, consentendo il confronto diretto tra entità. I punteggi vengono aggiornati continuamente quando sono disponibili nuovi dati.

Questa pagina è stata revisionata l'ultima volta il April 27, 2026. Versione dei dati: 1.0.

Documentazione completa della metodologia · Dati leggibili dalle macchine (JSON API)

Domande frequenti

Builder Agent è sicuro?
Usa con cautela. @gicm/builder-agent con un Punteggio di fiducia Nerq di 53.6/100 (D). Segnale più forte: conformità (100/100). Punteggio basato su multiple trust dimensioni.
Qual è il punteggio di fiducia di Builder Agent?
@gicm/builder-agent: 53.6/100 (D). Punteggio basato su multiple trust dimensioni. Compliance: 100/100. I punteggi si aggiornano quando nuovi dati diventano disponibili. API: GET nerq.ai/v1/preflight?target=@gicm/builder-agent
Quali sono alternative più sicure a Builder Agent?
Nella categoria Uncategorized, altri software tool sono in fase di analisi — ricontrolla presto. @gicm/builder-agent scores 53.6/100.
Con che frequenza viene aggiornato il punteggio di Builder Agent?
Nerq continuously monitors Builder Agent and updates its trust score as new data becomes available. Current: 53.6/100 (D), last verificato 2026-04-27. API: GET nerq.ai/v1/preflight?target=@gicm/builder-agent
Posso usare Builder Agent in un ambiente regolamentato?
Builder Agent non ha raggiunto la soglia di verifica Nerq di 70. Si consiglia ulteriore verifica.
API: /v1/preflight Trust Badge API Docs

Vedi anche

Disclaimer: I punteggi di fiducia Nerq sono valutazioni automatizzate basate su segnali disponibili pubblicamente. Non costituiscono raccomandazioni o garanzie. Effettua sempre la tua verifica personale.

Utilizziamo i cookie per analisi e caching. Privacy