Code Ingest은(는) 안전한가요?

Code Ingest — Nerq 신뢰 점수 71.3/100 (B 등급). 5개의 신뢰 차원 분석 결과, 대체로 안전하지만 일부 우려 사항이 있음으로 평가됩니다. 마지막 업데이트: 2026-03-31.

네, Code Ingest은(는) 사용하기에 안전합니다. Code Ingest is a software tool Nerq 신뢰 점수 71.3/100 (B), based on 5 independent data dimensions. It is recommended for use. Security: 0/100. Maintenance: 1/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. 기계 판독 가능 데이터 (JSON).

Code Ingest은(는) 안전한가요?

— Code Ingest 의 Nerq 신뢰 점수는 71.3/100 (B). 보안, 유지보수 및 커뮤니티 채택에서 강력한 신호로 Nerq 신뢰 기준을 충족합니다. Recommended for use — 구체적인 사항은 아래 전체 보고서를 참조하세요.

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

Code Ingest의 신뢰 점수는?

Code Ingest 의 Nerq 신뢰 점수는 71.3/100, earning a B grade. This score is based on 5 independently measured dimensions including security, maintenance, and community adoption.

보안
0
규정 준수
100
유지보수
1
문서화
1
인기도
0

Code Ingest의 주요 보안 발견 사항은?

Code Ingest's strongest signal is 규정 준수 at 100/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

보안 점수: 0/100 (weak)
Maintenance: 1/100 — low maintenance activity
Compliance: 100/100 — covers 52 of 52 jurisdictions
Documentation: 1/100 — limited documentation
Popularity: 0/100 — community adoption

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

개발자oikonai
카테고리coding
출처https://github.com/oikonai/code-ingest
Frameworksanthropic · mcp
Protocolsmcp · rest

규정 준수

EU AI Act Risk ClassMINIMAL
Compliance Score100/100
JurisdictionsAssessed across 52 jurisdictions

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 Code Ingest?

Code Ingest is a software tool in the coding category: Tool for ingesting code repos and mapping an MCP server over them. Nerq 신뢰 점수: 71/100 (B).

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 Code Ingest's Safety

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

The overall 신뢰 점수 of 71.3/100 (B) reflects the weighted combination of these signals. This exceeds the Nerq Verified threshold of 70, indicating the tool meets our standards for production use.

Who Should Use Code Ingest?

Code Ingest is designed for:

Risk guidance: Code Ingest meets the minimum threshold for production use, but we recommend monitoring for security advisories and keeping dependencies up to date. Consider implementing additional guardrails for sensitive workloads.

How to Verify Code Ingest'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's 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 Code Ingest's dependency tree.
  3. 리뷰 permissions — Understand what access Code Ingest requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Code Ingest 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=code-ingest
  6. 다음을 검토하세요: license — Confirm that Code Ingest'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 Code Ingest

When evaluating whether Code Ingest is safe, consider these category-specific risks:

Data handling

Understand how Code Ingest 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 Code Ingest's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

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

Third-party integrations

If Code Ingest 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 Code Ingest's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Code Ingest in violation of its license can expose your organization to legal liability.

Code Ingest and the EU AI Act

Code Ingest 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 Code Ingest Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Code Ingest?

Even well-trusted tools aren't right for every situation. Consider avoiding Code Ingest in these scenarios:

For each scenario, evaluate whether Code Ingest의 신뢰 점수 71.3/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.

How Code Ingest 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. Code Ingest's score of 71.3/100 is above the category average of 62/100.

This positions Code Ingest favorably among coding 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 Code Ingest 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, Code Ingest'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 Code Ingest's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=code-ingest&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 Code Ingest are strengthening or weakening over time.

Code Ingest vs Alternatives

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

주요 요점

자주 묻는 질문

Code Ingest은(는) 사용하기에 안전한가요?
네, 사용하기에 안전합니다. code-ingest 의 Nerq 신뢰 점수는 71.3/100 (B). 가장 강력한 신호: 규정 준수 (100/100). 점수 기반: security (0/100), maintenance (1/100), popularity (0/100), documentation (1/100).
Code Ingest's trust score이(가) 무엇인가요?
code-ingest: 71.3/100 (B). 점수 기반:: security (0/100), maintenance (1/100), popularity (0/100), documentation (1/100). Compliance: 100/100. 새로운 데이터가 제공되면 점수가 업데이트됩니다. API: GET nerq.ai/v1/preflight?target=code-ingest
Code Ingest의 더 안전한 대안은 무엇인가요?
coding 카테고리에서, 더 높은 평가를 받은 대안으로는 Significant-Gravitas/AutoGPT (75/100), ollama/ollama (74/100), langchain-ai/langchain (86/100). code-ingest의 점수는 71.3/100입니다.
How often is Code Ingest's safety score updated?
Nerq continuously monitors Code Ingest 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: 71.3/100 (B), last verified 2026-03-31. API: GET nerq.ai/v1/preflight?target=code-ingest
Code Ingest을(를) 규제 환경에서 사용할 수 있나요?
Yes — Code Ingest meets the Nerq Verified threshold (70+). Combine this with your internal security review for regulated deployments.
API: /v1/preflight Trust Badge API Docs

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

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