Code Remote é seguro?

Code Remote — Nerq Trust Score 35.5/100 (Grau E). Com base na análise de 3 dimensões de confiança, é tem riscos de segurança significativos. Última atualização: 2026-04-26.

Tenha cautela com Code Remote. Code Remote é um software tool com um Nerq Trust Score de 35.5/100 (E), com base em 3 dimensões de dados independentes. Abaixo do limiar verificado Nerq Manutenção: 0/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: 2026-04-26. Dados legíveis por máquina (JSON).

Code Remote é seguro?

NO — USE WITH CAUTION — Code Remote has a Nerq Trust Score of 35.5/100 (E). Possui sinais de confiança abaixo da média com lacunas significativas in segurança, manutenção, or documentação. Not recommended for production use without thorough manual review and additional segurança measures.

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

Qual é a pontuação de confiança de Code Remote?

Code Remote tem uma Pontuação de Confiança Nerq de 35.5/100, obtendo grau E. Esta pontuação é baseada em 3 dimensões medidas independentemente.

Manutenção
0
Documentação
0
Popularidade
0

Quais são as principais descobertas de segurança de Code Remote?

O sinal mais forte de Code Remote é manutenção com 0/100. Nenhuma vulnerabilidade conhecida foi detectada. Ainda não atingiu o limiar verificado Nerq de 70+.

Manutenção: 0/100 — baixa atividade de manutenção
Documentação: 0/100 — documentação limitada
Popularidade: 0/100 — 2 estrelas em pulsemcp

O que é Code Remote e quem o mantém?

Autorhttps://github.com/basicmachines-co/code-remote
CategoriaDevops
Stars2
Sourcehttps://github.com/basicmachines-co/code-remote

Alternativas Populares em devops

ansible/ansible
76.8/100 · B+
github
FlowiseAI/Flowise
63.3/100 · C+
github
shareAI-lab/learn-claude-code
69.2/100 · B-
github
continuedev/continue
64.4/100 · C+
github
wshobson/agents
70.5/100 · B
github

What Is Code Remote?

Code Remote is a DevOps tool: Enables secure remote command execution on your local machine.. It has 2 GitHub stars. Nerq Trust Score: 36/100 (E).

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 Code Remote's Safety

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

The overall Trust Score of 35.5/100 (E) 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 Remote?

Code Remote is designed for:

Risk guidance: We recommend caution with Code Remote. The low trust score suggests potential risks in segurança, manutenção, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Code Remote'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 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 Code Remote's dependency tree.
  3. Avaliação permissions — Understand what access Code Remote requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Code Remote 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=Code Remote
  6. Revise o/a license — Confirm that Code Remote'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 Code Remote

When evaluating whether Code Remote is safe, consider these category-specific risks:

Data handling

Understand how Code Remote 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 Code Remote'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 Code Remote. Segurança patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Code Remote 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 Code Remote'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 Remote in violation of its license can expose your organization to legal liability.

Best Practices for Using Code Remote Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for segurança advisories

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

When Should You Avoid Code Remote?

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

For each scenario, evaluate whether Code Remote's trust score of 35.5/100 meets your organization's risk tolerance. We recommend running a manual segurança assessment alongside the automated Nerq score.

How Code Remote Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Trust Score is 63/100. Code Remote's score of 35.5/100 is below the category average of 63/100.

This suggests that Code Remote trails behind many comparable DevOps tools. Organizations with strict segurança 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 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 Code Remote 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, Code Remote'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 Code Remote's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Code Remote&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 Code Remote are strengthening or weakening over time.

Code Remote vs Alternativas

In the devops category, Code Remote scores 35.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Pontos Principais

Análise Detalhada da Pontuação

DimensionScore
Manutenção0/100
Popularidade0/100

Baseado em 2 dimensões. Data from múltiplas fontes públicas incluindo registros de pacotes, GitHub, NVD, OSV.dev e OpenSSF Scorecard.

Quais dados Code Remote coleta?

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

Code Remote é seguro?

Segurança score: em avaliação. Review segurança practices and consider alternatives with higher segurança scores for sensitive use cases.

O Nerq monitora esta entidade contra NVD, OSV.dev e bancos de dados de vulnerabilidades específicos de registros para avaliação contínua de segurança.

Análise completa: Code Remote Relatório de Segurança

Como calculamos esta pontuação

Code Remote's trust score of 35.5/100 (E) é calculado a partir de múltiplas fontes públicas incluindo registros de pacotes, GitHub, NVD, OSV.dev e OpenSSF Scorecard. A pontuação reflete 2 dimensões independentes: manutenção (0/100), popularidade (0/100). Cada dimensão é ponderada igualmente para produzir a pontuação composta de confiança.

O Nerq analisa mais de 7,5 milhões de entidades em 26 registros usando a mesma metodologia, permitindo comparação direta entre entidades. As pontuações são atualizadas continuamente à medida que novos dados ficam disponíveis.

Esta página foi revisada pela última vez em April 26, 2026. Versão dos dados: 1.0.

Documentação completa da metodologia · Dados legíveis por máquina (API JSON)

Perguntas Frequentes

Code Remote é seguro?
Tenha cuidado. Code Remote com um Nerq Trust Score de 35.5/100 (E). Sinal mais forte: manutenção (0/100). Pontuação baseada em Manutenção (0/100), Popularidade (0/100), Documentação (0/100).
Qual é a pontuação de confiança de Code Remote?
Code Remote: 35.5/100 (E). Pontuação baseada em Manutenção (0/100), Popularidade (0/100), Documentação (0/100). As pontuações são atualizadas quando novos dados estão disponíveis. API: GET nerq.ai/v1/preflight?target=Code Remote
Quais são alternativas mais seguras ao Code Remote?
In the Devops category, higher-rated alternatives include ansible/ansible (77/100), FlowiseAI/Flowise (63/100), shareAI-lab/learn-claude-code (69/100). Code Remote scores 35.5/100.
Com que frequência o score de segurança do Code Remote é atualizado?
Nerq continuously monitors Code Remote and updates its trust score as new data becomes available. Current: 35.5/100 (E), last verificado 2026-04-26. API: GET nerq.ai/v1/preflight?target=Code Remote
Posso usar Code Remote em um ambiente regulado?
Code Remote não atingiu o limiar de verificação Nerq de 70. Diligência adicional recomendada.
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