Shellkeeper có an toàn không?
Shellkeeper — Nerq Điểm tin cậy 40.2/100 (Hạng E). Dựa trên phân tích 3 chiều tin cậy, được đánh giá là có những lo ngại bảo mật đáng chú ý. Cập nhật lần cuối: 2026-04-02.
Hãy thận trọng với Shellkeeper. Shellkeeper is a software tool với Điểm tin cậy Nerq là 40.2/100 (E), based on 3 tiêu chí dữ liệu độc lập. Dưới ngưỡng khuyến nghị là 70. Bảo trì: 0/100. Popularity: 0/100. Dữ liệu từ multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Cập nhật lần cuối: 2026-04-02. Dữ liệu máy đọc được (JSON).
Shellkeeper có an toàn không?
KHÔNG — SỬ DỤNG THẬN TRỌNG — Shellkeeper có Điểm tin cậy Nerq là 40.2/100 (E). Có tín hiệu tin cậy dưới trung bình với khoảng cách đáng kể về bảo mật, bảo trì hoặc tài liệu. Không khuyến nghị sử dụng trong sản xuất mà không có kiểm tra thủ công kỹ lưỡng và các biện pháp bảo mật bổ sung.
Điểm tin cậy của Shellkeeper là bao nhiêu?
Shellkeeper có Điểm tin cậy Nerq là 40.2/100, earning a E grade. This score is based on 3 independently measured tiêu chí including bảo mật, bảo trì, and sự chấp nhận của cộng đồng.
Các phát hiện bảo mật chính của Shellkeeper là gì?
Shellkeeper's strongest signal is bảo trì at 0/100. No lỗ hổng đã biết have been detected. It has not yet reached the Nerq Verified threshold of 70+.
Shellkeeper là gì và ai duy trì nó?
| Nhà phát triển | https://github.com/tranhuucanh/mcp-shellkeeper |
| Danh mục | devops |
| Sao | 28 |
| Nguồn | https://github.com/tranhuucanh/mcp-shellkeeper |
Lựa chọn phổ biến trong devops
What Is Shellkeeper?
Shellkeeper is a DevOps tool: ShellKeeper provides persistent terminal sessions for remote server administration.. It has 28 GitHub stars. Nerq Điểm tin cậy: 40/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bảo mật vulnerabilities, bảo trì activity, license tuân thủ, and sự chấp nhận của cộng đồng.
How Nerq Assesses Shellkeeper's Safety
Nerq's Điểm tin cậy is calculated from 13+ independent signals aggregated into five tiêu chí. Here is how Shellkeeper performs in each:
- Bảo trì (0/100): Shellkeeper is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API tài liệu, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Dựa trên GitHub stars, forks, download counts, and ecosystem integrations.
The overall Điểm tin cậy of 40.2/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 Shellkeeper?
Shellkeeper is designed for:
- Developers and teams working with devops tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Shellkeeper. The low trust score suggests potential risks in bảo mật, bảo trì, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Shellkeeper's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Xem xét repository bảo mật policy, open issues, and recent commits for signs of active bảo trì.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for lỗ hổng đã biết in Shellkeeper's dependency tree. - Đánh giá permissions — Understand what access Shellkeeper requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Shellkeeper in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=ShellKeeper - Xem xét license — Confirm that Shellkeeper'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.
- 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 bảo mật concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Shellkeeper
When evaluating whether Shellkeeper is safe, consider these category-specific risks:
Understand how Shellkeeper processes, stores, and transmits your data. Xem xét tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Shellkeeper's dependency tree for lỗ hổng đã biết. Tools with outdated or unmaintained dependencies pose a higher bảo mật risk.
Regularly check for updates to Shellkeeper. Bảo mật patches and bug fixes are only effective if you're running the latest version.
If Shellkeeper 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.
Verify that Shellkeeper's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Shellkeeper in violation of its license can expose your organization to legal liability.
Best Practices for Using Shellkeeper Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Shellkeeper while minimizing risk:
Periodically review how Shellkeeper is used in your workflow. Check for unexpected behavior, permissions drift, and tuân thủ with your bảo mật policies.
Ensure Shellkeeper and all its dependencies are running the latest stable versions to benefit from bảo mật patches.
Grant Shellkeeper only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Shellkeeper's bảo mật advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Shellkeeper is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Shellkeeper?
Even promising tools aren't right for every situation. Consider avoiding Shellkeeper in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional tuân thủ review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Shellkeeper là 40.2/100 meets your organization's risk tolerance. We recommend running a manual bảo mật assessment alongside the automated Nerq score.
How Shellkeeper Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Điểm tin cậy is 63/100. Shellkeeper's score of 40.2/100 is below the category average of 63/100.
This suggests that Shellkeeper trails behind many comparable DevOps tools. Organizations with strict bảo mật 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 trung bình 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.
Điểm tin cậy History
Nerq continuously monitors Shellkeeper and recalculates its Điểm tin cậy 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 bảo trì patterns change, Shellkeeper'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 bảo mật and quality. Conversely, a downward trend may signal reduced bảo trì, growing technical debt, or unresolved vulnerabilities. To track Shellkeeper's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=ShellKeeper&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 — bảo mật, bảo trì, tài liệu, tuân thủ, and community — has evolved independently, providing granular visibility into which aspects of Shellkeeper are strengthening or weakening over time.
Shellkeeper vs Lựa chọn thay thế
In the devops category, Shellkeeper scores 40.2/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Shellkeeper vs ansible — Điểm tin cậy: 84.3/100
- Shellkeeper vs Flowise — Điểm tin cậy: 76.9/100
- Shellkeeper vs learn-claude-code — Điểm tin cậy: 81.5/100
Điểm chính
- Shellkeeper has a Điểm tin cậy of 40.2/100 (E) and is not yet Nerq Verified.
- Shellkeeper has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among DevOps tools, Shellkeeper scores below the category average of 63/100, suggesting room for improvement relative to peers.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Câu hỏi thường gặp
Shellkeeper có an toàn để sử dụng không?
Shellkeeper's trust score là gì?
Các lựa chọn an toàn hơn Shellkeeper là gì?
How often is Shellkeeper's safety score updated?
Tôi có thể sử dụng Shellkeeper trong môi trường quy định không?
Disclaimer: Điểm tin cậy Nerq là đánh giá tự động dựa trên tín hiệu công khai. Đây không phải khuyến nghị hay bảo đảm. Hãy luôn tự xác minh.