Githubagentpush Dangerous Projects 1은(는) 안전한가요?
Githubagentpush Dangerous Projects 1 — Nerq Trust Score 64.6/100 (C 등급). 5개의 신뢰 차원 분석 결과, 대체로 안전하지만 일부 우려 사항이 있음으로 평가됩니다. 마지막 업데이트: 2026-04-05.
Githubagentpush Dangerous Projects 1을(를) 주의하며 사용하세요. Githubagentpush Dangerous Projects 1 은(는) software tool입니다 Nerq 신뢰 점수 64.6/100 (C), 5개의 독립적으로 측정된 데이터 차원 기반. Nerq 인증 기준 미달 보안: 0/100. 유지보수: 1/100. 인기도: 0/100. 패키지 레지스트리, GitHub, NVD, OSV.dev, OpenSSF Scorecard를 포함한 여러 공개 소스에서 수집된 데이터. 마지막 업데이트: 2026-04-05. 기계 판독 가능 데이터 (JSON).
Githubagentpush Dangerous Projects 1은(는) 안전한가요?
CAUTION — Githubagentpush Dangerous Projects 1 has a Nerq Trust Score of 64.6/100 (C). 보통 수준의 신뢰 신호가 있지만 일부 우려 사항이 있습니다 that warrant attention. Suitable for development use — review 보안 and 유지보수 signals before production deployment.
Githubagentpush Dangerous Projects 1의 신뢰 점수는?
Githubagentpush Dangerous Projects 1의 Nerq 신뢰 점수는 64.6/100이며 C 등급입니다. 이 점수는 보안, 유지보수, 커뮤니티 채택을 포함한 5개의 독립적으로 측정된 차원을 기반으로 합니다.
Githubagentpush Dangerous Projects 1의 주요 보안 발견 사항은?
Githubagentpush Dangerous Projects 1의 가장 강한 신호는 규정 준수이며 100/100입니다. 알려진 취약점이 감지되지 않았습니다. 아직 Nerq 인증 임계값 70+에 도달하지 못했습니다.
Githubagentpush Dangerous Projects 1은(는) 무엇이며 누가 관리하나요?
| 개발자 | divyanshu-iitian |
| 카테고리 | Devops |
| 출처 | https://github.com/divyanshu-iitian/GithubAgentPush-Dangerous-Projects-1 |
| Protocols | rest |
규정 준수
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 관할권s |
devops의 인기 대안
What Is Githubagentpush Dangerous Projects 1?
Githubagentpush Dangerous Projects 1 is a DevOps tool: SmartHomeHub is an AI-driven home automation system.. Nerq Trust Score: 65/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including 보안 vulnerabilities, 유지보수 activity, license 규정 준수, and 커뮤니티 채택.
How Nerq Assesses Githubagentpush Dangerous Projects 1's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 차원. Here is how Githubagentpush Dangerous Projects 1 performs in each:
- 보안 (0/100): Githubagentpush Dangerous Projects 1's 보안 posture is poor. This score factors in known CVEs, dependency vulnerabilities, 보안 policy presence, and code signing practices.
- 유지보수 (1/100): Githubagentpush Dangerous Projects 1 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 문서화, usage examples, and contribution guidelines.
- Compliance (100/100): Githubagentpush Dangerous Projects 1 is broadly compliant. Assessed against regulations in 52 관할권s including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. 기반: GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 64.6/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 Githubagentpush Dangerous Projects 1?
Githubagentpush Dangerous Projects 1 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: Githubagentpush Dangerous Projects 1 is suitable for development and testing environments. Before production deployment, conduct a thorough review of its 보안 posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.
How to Verify Githubagentpush Dangerous Projects 1's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — 다음을 검토하세요: repository's 보안 policy, open issues, and recent commits for signs of active 유지보수.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Githubagentpush Dangerous Projects 1's dependency tree. - 리뷰 permissions — Understand what access Githubagentpush Dangerous Projects 1 requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Githubagentpush Dangerous Projects 1 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=GithubAgentPush-Dangerous-Projects-1 - 다음을 검토하세요: license — Confirm that Githubagentpush Dangerous Projects 1'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 보안 concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Githubagentpush Dangerous Projects 1
When evaluating whether Githubagentpush Dangerous Projects 1 is safe, consider these category-specific risks:
Understand how Githubagentpush Dangerous Projects 1 processes, stores, and transmits your data. 다음을 검토하세요: tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Githubagentpush Dangerous Projects 1's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher 보안 risk.
Regularly check for updates to Githubagentpush Dangerous Projects 1. 보안 patches and bug fixes are only effective if you're running the latest version.
If Githubagentpush Dangerous Projects 1 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 Githubagentpush Dangerous Projects 1's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Githubagentpush Dangerous Projects 1 in violation of its license can expose your organization to legal liability.
Githubagentpush Dangerous Projects 1 and the EU AI Act
Githubagentpush Dangerous Projects 1 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 규정 준수 assessment covers 52 관할권s worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal 규정 준수.
Best Practices for Using Githubagentpush Dangerous Projects 1 Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Githubagentpush Dangerous Projects 1 while minimizing risk:
Periodically review how Githubagentpush Dangerous Projects 1 is used in your workflow. Check for unexpected behavior, permissions drift, and 규정 준수 with your 보안 policies.
Ensure Githubagentpush Dangerous Projects 1 and all its dependencies are running the latest stable versions to benefit from 보안 patches.
Grant Githubagentpush Dangerous Projects 1 only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Githubagentpush Dangerous Projects 1's 보안 advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Githubagentpush Dangerous Projects 1 is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Githubagentpush Dangerous Projects 1?
Even promising tools aren't right for every situation. Consider avoiding Githubagentpush Dangerous Projects 1 in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional 규정 준수 review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Githubagentpush Dangerous Projects 1's trust score of 64.6/100 meets your organization's risk tolerance. We recommend running a manual 보안 assessment alongside the automated Nerq score.
How Githubagentpush Dangerous Projects 1 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. Githubagentpush Dangerous Projects 1's score of 64.6/100 is above the category average of 63/100.
This positions Githubagentpush Dangerous Projects 1 favorably among DevOps tools. While it outperforms the average, there is still room for improvement in certain trust 차원.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks 보통 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 Githubagentpush Dangerous Projects 1 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 유지보수 patterns change, Githubagentpush Dangerous Projects 1'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 보안 and quality. Conversely, a downward trend may signal reduced 유지보수, growing technical debt, or unresolved vulnerabilities. To track Githubagentpush Dangerous Projects 1's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GithubAgentPush-Dangerous-Projects-1&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 — 보안, 유지보수, 문서화, 규정 준수, and community — has evolved independently, providing granular visibility into which aspects of Githubagentpush Dangerous Projects 1 are strengthening or weakening over time.
Githubagentpush Dangerous Projects 1 vs 대안
In the devops category, Githubagentpush Dangerous Projects 1 scores 64.6/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Githubagentpush Dangerous Projects 1 vs ansible — Trust Score: 84.3/100
- Githubagentpush Dangerous Projects 1 vs Flowise — Trust Score: 76.9/100
- Githubagentpush Dangerous Projects 1 vs learn-claude-code — Trust Score: 81.5/100
주요 요점
- Githubagentpush Dangerous Projects 1 has a Trust Score of 64.6/100 (C) and is not yet Nerq Verified.
- Githubagentpush Dangerous Projects 1 shows 보통 trust signals. Conduct thorough due diligence before deploying to production environments.
- Among DevOps tools, Githubagentpush Dangerous Projects 1 scores above the category average of 63/100, demonstrating above-average reliability.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
자주 묻는 질문
Githubagentpush Dangerous Projects 1은(는) 안전한가요?
Githubagentpush Dangerous Projects 1의 신뢰 점수는?
What are safer alternatives to Githubagentpush Dangerous Projects 1?
How often is Githubagentpush Dangerous Projects 1's safety score updated?
Can I use Githubagentpush Dangerous Projects 1 in a regulated environment?
참고 항목
Disclaimer: Nerq 신뢰 점수는 공개적으로 사용 가능한 신호를 기반으로 한 자동 평가입니다. 추천이나 보증이 아닙니다. 항상 직접 확인하세요.