Stack Chan은(는) 안전한가요?
Stack Chan을(를) 주의하며 사용하세요. Stack Chan is a software tool Nerq 신뢰 점수 67.2/100 (C), based on 5 independent data dimensions. 권장 기준인 70 미만입니다. Security: 0/100. 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-03-29. 기계 판독 가능 데이터 (JSON).
Stack Chan은(는) 안전한가요?
주의 — Stack Chan 의 Nerq 신뢰 점수는 67.2/100 (C). 보통 수준의 신뢰 신호가 있지만 주의가 필요한 일부 우려 사항이 있습니다. 개발 사용에 적합 — 프로덕션 배포 전 보안 및 유지보수 신호를 검토하세요.
신뢰 점수 세부 정보
주요 발견
세부 정보
| 개발자 | stack-chan |
| 카테고리 | infrastructure |
| 스타 | 1,220 |
| 출처 | https://github.com/stack-chan/stack-chan |
| Protocols | mcp |
규정 준수
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 87/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
infrastructure의 인기 대안
What Is Stack Chan?
Stack Chan is a software tool in the infrastructure category: A JavaScript-driven M5Stack-embedded super-kawaii robot.. It has 1,220 GitHub stars. Nerq 신뢰 점수: 67/100 (C).
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 Stack Chan's Safety
Nerq's 신뢰 점수 is calculated from 13+ independent signals aggregated into five dimensions. Here is how Stack Chan performs in each:
- 보안 (0/100): Stack Chan's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
- 유지보수 (0/100): Stack Chan 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 documentation, usage examples, and contribution guidelines.
- Compliance (87/100): Stack Chan is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (1/100): Community adoption is limited. Based on GitHub stars, forks, download counts, and ecosystem integrations.
The overall 신뢰 점수 of 67.2/100 (C) 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 Stack Chan?
Stack Chan is designed for:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Stack Chan is suitable for development and testing environments. Before production deployment, conduct a thorough review of its security posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.
How to Verify Stack Chan's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Stack Chan's dependency tree. - 리뷰 permissions — Understand what access Stack Chan requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Stack Chan 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=stack-chan - 다음을 검토하세요: license — Confirm that Stack Chan'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 security concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Stack Chan
When evaluating whether Stack Chan is safe, consider these category-specific risks:
Understand how Stack Chan processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Stack Chan's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Stack Chan. Security patches and bug fixes are only effective if you're running the latest version.
If Stack Chan 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 Stack Chan's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Stack Chan in violation of its license can expose your organization to legal liability.
Stack Chan and the EU AI Act
Stack Chan 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 compliance assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.
Best Practices for Using Stack Chan Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Stack Chan while minimizing risk:
Periodically review how Stack Chan is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Stack Chan and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Stack Chan only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Stack Chan's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Stack Chan is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Stack Chan?
Even promising tools aren't right for every situation. Consider avoiding Stack Chan in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional compliance review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Stack Chan의 신뢰 점수 67.2/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.
How Stack Chan Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average 신뢰 점수 is 62/100. Stack Chan's score of 67.2/100 is above the category average of 62/100.
This positions Stack Chan favorably among infrastructure tools. While it outperforms the average, there is still room for improvement in certain trust dimensions.
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 Stack Chan 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, Stack Chan'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 Stack Chan's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=stack-chan&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 Stack Chan are strengthening or weakening over time.
Stack Chan vs Alternatives
infrastructure 카테고리에서, Stack Chan의 점수는 67.2/100입니다. There are higher-scoring alternatives available. For a detailed comparison, see:
- Stack Chan vs n8n — 신뢰 점수: 78.5/100
- Stack Chan vs langflow — 신뢰 점수: 87.6/100
- Stack Chan vs dify — 신뢰 점수: 79.1/100
주요 요점
- Stack Chan has a 신뢰 점수 of 67.2/100 (C) and is not yet Nerq Verified.
- Stack Chan shows moderate trust signals. Conduct thorough due diligence before deploying to production environments.
- Among infrastructure tools, Stack Chan scores above the category average of 62/100, demonstrating above-average reliability.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
자주 묻는 질문
Stack Chan은(는) 사용하기에 안전한가요?
Stack Chan's trust score이(가) 무엇인가요?
Stack Chan의 더 안전한 대안은 무엇인가요?
How often is Stack Chan's safety score updated?
Stack Chan을(를) 규제 환경에서 사용할 수 있나요?
Disclaimer: Nerq 신뢰 점수는 공개적으로 사용 가능한 신호를 기반으로 한 자동 평가입니다. 추천이나 보증이 아닙니다. 항상 직접 확인하세요.