Github Repo Extractor은(는) 안전한가요?

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

Github Repo Extractor에 대해 주의하세요. Github Repo Extractor 은(는) software tool입니다 Nerq 신뢰 점수 43.4/100 (E), 3개의 독립적으로 측정된 데이터 차원 기반. 권장 기준인 70 미만입니다. 유지보수: 0/100. 인기도: 0/100. multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard에서 수집된 데이터. 마지막 업데이트: 2026-04-03. 기계 판독 가능 데이터 (JSON).

Github Repo Extractor은(는) 안전한가요?

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

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

Github Repo Extractor의 신뢰 점수는?

Github Repo Extractor의 Nerq 신뢰 점수는 43.4/100이며 E 등급입니다. 이 점수는 보안, 유지보수, 커뮤니티 채택을 포함한 3개의 독립적으로 측정된 차원을 기반으로 합니다.

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

Github Repo Extractor의 주요 보안 발견 사항은?

Github Repo Extractor의 가장 강한 신호는 유지보수이며 0/100입니다. 알려진 취약점이 감지되지 않았습니다. 아직 Nerq 인증 임계값 70+에 도달하지 못했습니다.

유지보수: 0/100 — 유지보수 활동 저조
Documentation: 0/100 — 제한된 문서화
인기도: 0/100 — 6 스타 수: pulsemcp

Github Repo Extractor은(는) 무엇이며 누가 관리하나요?

개발자https://github.com/kazuph/mcp-github-pera1
카테고리coding
스타6
출처https://github.com/kazuph/mcp-github-pera1

coding의 인기 대안

Significant-Gravitas/AutoGPT
74.7/100 · B
github
ollama/ollama
73.8/100 · B
github
langchain-ai/langchain
86.4/100 · A
github
x1xhlol/system-prompts-and-models-of-ai-tools
73.8/100 · B
github
anomalyco/opencode
87.9/100 · A
github

What Is Github Repo Extractor?

Github Repo Extractor is a software tool in the coding category: Connects to GitHub repositories for code-related queries.. It has 6 GitHub stars. Nerq 신뢰 점수: 43/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including 보안 vulnerabilities, 유지보수 activity, license 규정 준수, and 커뮤니티 채택.

How Nerq Assesses Github Repo Extractor's Safety

Nerq's 신뢰 점수 is calculated from 13+ independent signals aggregated into five 차원. Here is how Github Repo Extractor performs in each:

The overall 신뢰 점수 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 Github Repo Extractor?

Github Repo Extractor is designed for:

Risk guidance: We recommend caution with Github Repo Extractor. The low trust score suggests potential risks in 보안, 유지보수, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Github Repo Extractor's Safety Yourself

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

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

Common Safety Concerns with Github Repo Extractor

When evaluating whether Github Repo Extractor is safe, consider these category-specific risks:

Data handling

Understand how Github Repo Extractor processes, stores, and transmits your data. 다음을 검토하세요: tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency 보안

Check Github Repo Extractor's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher 보안 risk.

Update frequency

Regularly check for updates to Github Repo Extractor. 보안 patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Github Repo Extractor 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 규정 준수

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

Best Practices for Using Github Repo Extractor Safely

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

Conduct regular audits

Periodically review how Github Repo Extractor is used in your workflow. Check for unexpected behavior, permissions drift, and 규정 준수 with your 보안 policies.

Keep dependencies updated

Ensure Github Repo Extractor and all its dependencies are running the latest stable versions to benefit from 보안 patches.

Follow least privilege

Grant Github Repo Extractor only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for 보안 advisories

Subscribe to Github Repo Extractor's 보안 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 Github Repo Extractor is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Github Repo Extractor?

Even promising tools aren't right for every situation. Consider avoiding Github Repo Extractor in these scenarios:

For each scenario, evaluate whether Github Repo Extractor의 신뢰 점수 43.4/100 meets your organization's risk tolerance. We recommend running a manual 보안 assessment alongside the automated Nerq score.

How Github Repo Extractor Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average 신뢰 점수 is 62/100. Github Repo Extractor's score of 43.4/100 is below the category average of 62/100.

This suggests that Github Repo Extractor trails behind many comparable coding tools. Organizations with strict 보안 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 보통 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 Github Repo Extractor 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 유지보수 patterns change, Github Repo Extractor'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 Github Repo Extractor's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GitHub Repo Extractor&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 Github Repo Extractor are strengthening or weakening over time.

Github Repo Extractor vs 대안

coding 카테고리에서, Github Repo Extractor의 점수는 43.4/100입니다. There are higher-scoring alternatives available. For a detailed comparison, see:

주요 요점

자주 묻는 질문

Github Repo Extractor은(는) 사용하기에 안전한가요?
주의하세요. GitHub Repo Extractor 의 Nerq 신뢰 점수는 43.4/100 (E). 가장 강력한 신호: 유지보수 (0/100). 점수 기반: 유지보수 (0/100), 인기도 (0/100), 문서화 (0/100).
Github Repo Extractor's trust score이(가) 무엇인가요?
GitHub Repo Extractor: 43.4/100 (E). 점수 기반:: 유지보수 (0/100), 인기도 (0/100), 문서화 (0/100). 새로운 데이터가 제공되면 점수가 업데이트됩니다. API: GET nerq.ai/v1/preflight?target=GitHub Repo Extractor
Github Repo Extractor의 더 안전한 대안은 무엇인가요?
coding 카테고리에서, 더 높은 평가를 받은 대안으로는 Significant-Gravitas/AutoGPT (75/100), ollama/ollama (74/100), langchain-ai/langchain (86/100). GitHub Repo Extractor의 점수는 43.4/100입니다.
How often is Github Repo Extractor's safety score updated?
Nerq continuously monitors Github Repo Extractor and updates its trust score as new data becomes available. 데이터 출처: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 43.4/100 (E), last 인증됨 2026-04-03. API: GET nerq.ai/v1/preflight?target=GitHub Repo Extractor
Github Repo Extractor을(를) 규제 환경에서 사용할 수 있나요?
Github Repo Extractor 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