Coding Todo é seguro?

Coding Todo — Nerq Trust Score 43.4/100 (Grau E). Com base na análise de 3 dimensões de confiança, é tem preocupações de segurança notáveis. Última atualização: 2026-04-05.

Tenha cautela com Coding Todo. Coding Todo é um software tool com um Nerq Trust Score de 43.4/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-05. Dados legíveis por máquina (JSON).

Coding Todo é seguro?

NO — USE WITH CAUTION — Coding Todo has a Nerq Trust Score of 43.4/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 Coding Todo?

Coding Todo tem uma Pontuação de Confiança Nerq de 43.4/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 Coding Todo?

O sinal mais forte de Coding Todo é 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 — 1 estrelas em pulsemcp

O que é Coding Todo e quem o mantém?

Autorhttps://github.com/dennismartis/mcp-todo
CategoriaProductivity
Stars1
Sourcehttps://github.com/dennismartis/mcp-todo

Alternativas Populares em productivity

CherryHQ/cherry-studio
84.5/100 · A
github
ToolJet/ToolJet
90.9/100 · A+
github
PostHog/posthog
74.7/100 · B
github
claude-task-master
67.8/100 · C
mcp
iOfficeAI/AionUi
84.4/100 · A
github

What Is Coding Todo?

Coding Todo is a software tool in the productivity category: Coding Todo integrates project management tools for efficient task tracking and AI-assisted prioritization in software development workflows.. It has 1 GitHub stars. Nerq Trust Score: 43/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 Coding Todo's Safety

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

The overall Trust Score of 43.4/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 Coding Todo?

Coding Todo is designed for:

Risk guidance: We recommend caution with Coding Todo. 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 Coding Todo'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 Coding Todo's dependency tree.
  3. Avaliação permissions — Understand what access Coding Todo requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Coding Todo 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=Coding Todo
  6. Revise o/a license — Confirm that Coding Todo'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 Coding Todo

When evaluating whether Coding Todo is safe, consider these category-specific risks:

Data handling

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

Third-party integrations

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

Best Practices for Using Coding Todo Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for segurança advisories

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

When Should You Avoid Coding Todo?

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

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

How Coding Todo Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among productivity tools, the average Trust Score is 62/100. Coding Todo's score of 43.4/100 is below the category average of 62/100.

This suggests that Coding Todo trails behind many comparable productivity 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 Coding Todo 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, Coding Todo'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 Coding Todo's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Coding Todo&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 Coding Todo are strengthening or weakening over time.

Coding Todo vs Alternativas

In the productivity category, Coding Todo scores 43.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Pontos Principais

Perguntas Frequentes

Coding Todo é seguro?
Tenha cuidado. Coding Todo com um Nerq Trust Score de 43.4/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 Coding Todo?
Coding Todo: 43.4/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=Coding Todo
What are safer alternatives to Coding Todo?
In the Productivity category, higher-rated alternatives include CherryHQ/cherry-studio (84/100), ToolJet/ToolJet (91/100), PostHog/posthog (75/100). Coding Todo scores 43.4/100.
How often is Coding Todo's safety score updated?
Nerq continuously monitors Coding Todo and updates its trust score as new data becomes available. Dados obtidos de múltiplas fontes públicas incluindo registros de pacotes, GitHub, NVD, OSV.dev e OpenSSF Scorecard. Current: 43.4/100 (E), last verificado 2026-04-05. API: GET nerq.ai/v1/preflight?target=Coding Todo
Can I use Coding Todo in a regulated environment?
Coding Todo has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
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