Clean Apex é seguro?

Clean Apex — Nerq Trust Score 59.2/100 (Grau D). Pontuação baseada em 5 independent trust signals.

Clean Apex é um software tool com um Nerq Trust Score de 59.2/100 (D), com base em 5 dimensões de dados independentes. Segurança: 0/100. Manutenção: 1/100. Popularidade: 0/100. Dados obtidos de múltiplas fontes públicas incluindo registros de pacotes, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Última atualização: n/a. Dados legíveis por máquina (JSON).

Clean Apex é seguro?

Detalhamento da Pontuação de Confiança — Clean Apex has a Nerq Trust Score of 59.2/100 (D). Measured across 5 independent trust signals.

Análise de Segurança → Relatório de Privacidade →

Qual é a pontuação de confiança de Clean Apex?

Clean Apex tem uma Pontuação de Confiança Nerq de 59.2/100, obtendo grau D. Esta pontuação é baseada em 5 dimensões medidas independentemente.

Segurança
0
Compliance
100
Manutenção
1
Documentação
1
Popularidade
0

Quais são as principais descobertas de segurança de Clean Apex?

O sinal mais forte de Clean Apex é conformidade com 100/100. Nenhuma vulnerabilidade conhecida foi detectada.

⚠Pontuação de segurança: 0/100 (fraco)
⚠Manutenção: 1/100 — baixa atividade de manutenção
⚠Compliance: 100/100 — covers 52 of 52 jurisdictions
⚠Documentação: 1/100 — documentação limitada
⚠Popularidade: 0/100 — adoção comunitária

O que é Clean Apex e quem o mantém?

Autorxixiaofinland
CategoriaCoding
Sourcehttps://github.com/xixiaofinland/clean-apex
Frameworksopenai · anthropic
Protocolsrest

Conformidade Regulatória

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

Alternativas Populares em coding

Significant-Gravitas/AutoGPT
65.3/100 · C
github
ollama/ollama
64.4/100 · C
github
langchain-ai/langchain
77.0/100 · B
github
x1xhlol/system-prompts-and-models-of-ai-tools
64.4/100 · C
github
anomalyco/opencode
78.5/100 · B
github

What Is Clean Apex?

Clean Apex is a software tool in the coding category: An opinionated agent skill for Apex clean code guidance.. Nerq Trust Score: 59/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including segurança vulnerabilities, manutenção activity, license conformidade, and adoção pela comunidade.

How Nerq Assesses Clean Apex's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensões. Here is how Clean Apex performs in each:

The overall Trust Score of 59.2/100 (D) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.

Who Typically Evaluates Clean Apex?

Clean Apex is commonly evaluated by:

How to read the signals: Clean Apex's measured signals (segurança 0/100, manutenção 1/100, documentação 1/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.

How to Verify Clean Apex's Safety Yourself

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

  1. Check the source code — Revise o/a repository's segurança policy, open issues, and recent commits for signs of active manutenção.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Clean Apex's dependency tree.
  3. Avaliação permissions — Understand what access Clean Apex requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Clean Apex 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=clean-apex
  6. Revise o/a license — Confirm that Clean Apex'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 segurança concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Clean Apex

When evaluating whether Clean Apex is safe, consider these category-specific risks:

Data handling

Understand how Clean Apex processes, stores, and transmits your data. Revise o/a tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency segurança

Check Clean Apex's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher segurança risk.

Update frequency

Regularly check for updates to Clean Apex. Segurança patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Clean Apex 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 conformidade

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

Clean Apex and the EU AI Act

Clean Apex 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 conformidade assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal conformidade.

Best Practices for Using Clean Apex Safely

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

Conduct regular audits

Periodically review how Clean Apex is used in your workflow. Check for unexpected behavior, permissions drift, and conformidade with your segurança policies.

Keep dependencies updated

Ensure Clean Apex and all its dependencies are running the latest stable versions to benefit from segurança patches.

Follow least privilege

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

Monitor for segurança advisories

Subscribe to Clean Apex's segurança 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 Clean Apex is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Clean Apex

Nerq's signals are one input. In the following situations, evaluate Clean Apex's measured signals against your own requirements before making a decision:

For each situation, compare Clean Apex's measured trust score of 59.2/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Clean Apex is suitable for any particular use.

How Clean Apex 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. Clean Apex's score of 59.2/100 is near the category average of 62/100.

This places Clean Apex in line with the typical coding 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 moderado 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 Clean Apex 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 manutenção patterns change, Clean Apex'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 segurança and quality. Conversely, a downward trend may signal reduced manutenção, growing technical debt, or unresolved vulnerabilities. To track Clean Apex's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=clean-apex&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 — segurança, manutenção, documentação, conformidade, and community — has evolved independently, providing granular visibility into which aspects of Clean Apex are strengthening or weakening over time.

Clean Apex vs Alternativas

In the coding category, Clean Apex scores 59.2/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Pontos Principais

Perguntas Frequentes

Clean Apex é seguro?
clean-apex com um Nerq Trust Score de 59.2/100 (D). Sinal mais forte: conformidade (100/100). Pontuação baseada em Segurança (0/100), Manutenção (1/100), Popularidade (0/100), Documentação (1/100).
Qual é a pontuação de confiança de Clean Apex?
clean-apex: 59.2/100 (D). Pontuação baseada em Segurança (0/100), Manutenção (1/100), Popularidade (0/100), Documentação (1/100). Compliance: 100/100. As pontuações são atualizadas quando novos dados estão disponíveis. API: GET nerq.ai/v1/preflight?target=clean-apex
Quais são alternativas mais seguras ao Clean Apex?
In the Coding category, higher-rated alternatives include Significant-Gravitas/AutoGPT (65/100), ollama/ollama (64/100), langchain-ai/langchain (77/100). clean-apex scores 59.2/100.
Com que frequência o score de segurança do Clean Apex é atualizado?
Nerq recomputes Clean Apex's trust score as new data becomes available. Current: 59.2/100 (D). API: GET nerq.ai/v1/preflight?target=clean-apex
Posso usar Clean Apex em um ambiente regulado?
Clean Apex: 59.2/100 (D). Compliance: 52 of 52 jurisdictions. EU AI Act compliant. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Veja também

Disclaimer: As pontuações de confiança da Nerq são avaliações automatizadas baseadas em sinais publicamente disponíveis. Não são endossos ou garantias. Sempre realize sua própria verificação.

Usamos cookies para análise e cache. Privacidade