Cli Secure은(는) 안전한가요?

Cli Secure — Nerq 신뢰 점수 43.5/100 (E 등급). 3개의 신뢰 차원 분석 결과, 주목할 만한 보안 우려가 있음으로 평가됩니다. 마지막 업데이트: 2026-04-01.

Cli Secure에 대해 주의하세요. Cli Secure is a software tool Nerq 신뢰 점수 43.5/100 (E), based on 3 independent data dimensions. 권장 기준인 70 미만입니다. Maintenance: 0/100. Popularity: 1/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. 기계 판독 가능 데이터 (JSON).

Cli Secure은(는) 안전한가요?

아니오 — 주의하며 사용 — Cli Secure 의 Nerq 신뢰 점수는 43.5/100 (E). 보안, 유지보수 또는 문서화에서 심각한 격차와 함께 평균 이하의 신뢰 신호가 있습니다. 철저한 수동 검토 및 추가 보안 조치 없이는 프로덕션 사용이 권장되지 않습니다.

보안 분석 → {name} 개인정보 보고서 →

Cli Secure의 신뢰 점수는?

Cli Secure 의 Nerq 신뢰 점수는 43.5/100, earning a E grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.

유지보수
0
문서화
0
인기도
1

Cli Secure의 주요 보안 발견 사항은?

Cli Secure's strongest signal is 인기도 at 1/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Maintenance: 0/100 — low maintenance activity
Documentation: 0/100 — limited documentation
Popularity: 1/100 — 166 stars on pulsemcp

Cli Secure은(는) 무엇이며 누가 관리하나요?

개발자https://github.com/mladensu/cli-mcp-server
카테고리보안
스타166
출처https://github.com/mladensu/cli-mcp-server

security의 인기 대안

bee-san/Ciphey
73.8/100 · B
github
usestrix/strix
73.8/100 · B
github
SWE-agent/SWE-agent
91.3/100 · A+
github
promptfoo/promptfoo
92.6/100 · A+
github
TecharoHQ/anubis
72.3/100 · B
github

What Is Cli Secure?

Cli Secure is a security tool: CLI Secure executes shell commands with strict security policies.. It has 166 GitHub stars. Nerq 신뢰 점수: 44/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses Cli Secure's Safety

Nerq's 신뢰 점수 is calculated from 13+ independent signals aggregated into five dimensions. Here is how Cli Secure performs in each:

The overall 신뢰 점수 of 43.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 Cli Secure?

Cli Secure is designed for:

Risk guidance: We recommend caution with Cli Secure. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Cli Secure's Safety Yourself

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

  1. Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Cli Secure's dependency tree.
  3. 리뷰 permissions — Understand what access Cli Secure requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Cli Secure 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=CLI Secure
  6. 다음을 검토하세요: license — Confirm that Cli Secure'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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Cli Secure

When evaluating whether Cli Secure is safe, consider these category-specific risks:

Data handling

Understand how Cli Secure processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Cli Secure's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Cli Secure. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Cli Secure 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 compliance

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

Best Practices for Using Cli Secure Safely

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

Conduct regular audits

Periodically review how Cli Secure is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Cli Secure and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Cli Secure?

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

For each scenario, evaluate whether Cli Secure의 신뢰 점수 43.5/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Cli Secure Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among security tools, the average 신뢰 점수 is 67/100. Cli Secure's score of 43.5/100 is below the category average of 67/100.

This suggests that Cli Secure trails behind many comparable security tools. Organizations with strict security 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 moderate 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.

신뢰 점수 History

Nerq continuously monitors Cli Secure and recalculates its 신뢰 점수 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 maintenance patterns change, Cli Secure'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 security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Cli Secure's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=CLI Secure&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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Cli Secure are strengthening or weakening over time.

Cli Secure vs Alternatives

보안 카테고리에서, Cli Secure의 점수는 43.5/100입니다. There are higher-scoring alternatives available. For a detailed comparison, see:

주요 요점

자주 묻는 질문

Cli Secure은(는) 사용하기에 안전한가요?
주의하세요. CLI Secure 의 Nerq 신뢰 점수는 43.5/100 (E). 가장 강력한 신호: 인기도 (1/100). 점수 기반: maintenance (0/100), popularity (1/100), documentation (0/100).
Cli Secure's trust score이(가) 무엇인가요?
CLI Secure: 43.5/100 (E). 점수 기반:: maintenance (0/100), popularity (1/100), documentation (0/100). 새로운 데이터가 제공되면 점수가 업데이트됩니다. API: GET nerq.ai/v1/preflight?target=CLI Secure
Cli Secure의 더 안전한 대안은 무엇인가요?
보안 카테고리에서, 더 높은 평가를 받은 대안으로는 bee-san/Ciphey (74/100), usestrix/strix (74/100), SWE-agent/SWE-agent (91/100). CLI Secure의 점수는 43.5/100입니다.
How often is Cli Secure's safety score updated?
Nerq continuously monitors Cli Secure and updates its trust score as new data becomes available. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 43.5/100 (E), last verified 2026-04-01. API: GET nerq.ai/v1/preflight?target=CLI Secure
Cli Secure을(를) 규제 환경에서 사용할 수 있나요?
Cli Secure has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq 신뢰 점수는 공개적으로 사용 가능한 신호를 기반으로 한 자동 평가입니다. 추천이나 보증이 아닙니다. 항상 직접 확인하세요.

We use cookies for analytics and caching. 개인정보 Policy