Api200은(는) 안전한가요?

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

Api200을(를) 주의하며 사용하세요. Api200 is a software tool Nerq 신뢰 점수 62.9/100 (C), based on 4 independent data dimensions. 권장 기준인 70 미만입니다. 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-04-02. 기계 판독 가능 데이터 (JSON).

Api200은(는) 안전한가요?

주의 — Api200 의 Nerq 신뢰 점수는 62.9/100 (C). 보통 수준의 신뢰 신호가 있지만 주의가 필요한 일부 우려 사항이 있습니다. 개발 사용에 적합 — 프로덕션 배포 전 보안 및 유지보수 신호를 검토하세요.

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

Api200의 신뢰 점수는?

Api200 의 Nerq 신뢰 점수는 62.9/100, earning a C grade. This score is based on 4 independently measured dimensions including security, maintenance, and community adoption.

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

Api200의 주요 보안 발견 사항은?

Api200's strongest signal is 규정 준수 at 100/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Maintenance: 0/100 — low maintenance activity
Compliance: 100/100 — covers 52 of 52 jurisdictions
Documentation: 0/100 — limited documentation
Popularity: 1/100 — 257 stars on mcp_registry

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

개발자API-200
카테고리infrastructure
스타257
출처https://github.com/API-200/api200
Protocolsmcp

규정 준수

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

infrastructure의 인기 대안

n8n-io/n8n
78.5/100 · B
github
langflow-ai/langflow
87.6/100 · A
github
langgenius/dify
79.1/100 · B
github
open-webui/open-webui
74.8/100 · B
github
google-gemini/gemini-cli
71.8/100 · B
github

What Is Api200?

Api200 is a software tool in the infrastructure category: API 200 is an open source API gateway to simplify 3rd-party integrations. Import endpoints, set up caching, retries, and mocks. Access all services via one URL. Monitor logs, track errors, and get alerts on API incidents.. It has 257 GitHub stars. Nerq 신뢰 점수: 63/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 Api200's Safety

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

The overall 신뢰 점수 of 62.9/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 Api200?

Api200 is designed for:

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

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

Data handling

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

Update frequency

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

Third-party integrations

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

Best Practices for Using Api200 Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Api200?

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

For each scenario, evaluate whether Api200의 신뢰 점수 62.9/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

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

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

Api200 vs Alternatives

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

주요 요점

자주 묻는 질문

Api200은(는) 사용하기에 안전한가요?
주의하며 사용하세요. api200 의 Nerq 신뢰 점수는 62.9/100 (C). 가장 강력한 신호: 규정 준수 (100/100). 점수 기반: maintenance (0/100), popularity (1/100), documentation (0/100).
Api200's trust score이(가) 무엇인가요?
api200: 62.9/100 (C). 점수 기반:: maintenance (0/100), popularity (1/100), documentation (0/100). Compliance: 100/100. 새로운 데이터가 제공되면 점수가 업데이트됩니다. API: GET nerq.ai/v1/preflight?target=api200
Api200의 더 안전한 대안은 무엇인가요?
infrastructure 카테고리에서, 더 높은 평가를 받은 대안으로는 n8n-io/n8n (78/100), langflow-ai/langflow (88/100), langgenius/dify (79/100). api200의 점수는 62.9/100입니다.
How often is Api200's safety score updated?
Nerq continuously monitors Api200 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: 62.9/100 (C), last verified 2026-04-02. API: GET nerq.ai/v1/preflight?target=api200
Api200을(를) 규제 환경에서 사용할 수 있나요?
Api200 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