Är Api200 säker?

Api200 — Nerq Trust Score 62.9/100 (Betyg C). Baserat på analys av 4 tillitsdimensioner bedöms det som generellt säkert men med vissa farhågor. Senast uppdaterad: 2026-04-08.

Använd Api200 med försiktighet. Api200 är en programvara med ett Nerq-förtroendepoäng på 62.9/100 (C), baserat på 4 oberoende datadimensioner. Under Nerqs verifierade tröskel Underhåll: 0/100. Popularitet: 1/100. Data hämtad från flera offentliga källor inklusive paketregister, GitHub, NVD, OSV.dev och OpenSSF Scorecard. Senast uppdaterad: 2026-04-08. Maskinläsbar data (JSON).

Är Api200 säker?

CAUTION — Api200 has a Nerq Trust Score of 62.9/100 (C). Har måttliga förtroendesignaler men uppvisar vissa oroande områden that warrant attention. Suitable for development use — review säkerhet and underhåll signals before production deployment.

Säkerhetsanalys → Api200 integritetsrapport →

Vad är Api200s förtroendepoäng?

Api200 har ett Nerq-förtroendepoäng på 62.9/100 med betyget C. Denna poäng baseras på 4 oberoende mätta dimensioner inklusive säkerhet, underhåll och communityanvändning.

Regelefterlevnad
100
Underhåll
0
Dokumentation
0
Popularitet
1

Vilka är de viktigaste säkerhetsresultaten för Api200?

Api200s starkaste signal är regelefterlevnad på 100/100. Inga kända sårbarheter har upptäckts. Har ännu inte nått Nerqs verifieringströskel på 70+.

Underhåll: 0/100 — låg underhållsaktivitet
Regelefterlevnad: 100/100 — covers 52 of 52 jurisdiktions
Dokumentation: 0/100 — begränsad dokumentation
Popularitet: 1/100 — 257 stjärnor på mcp registry

Vad är Api200 och vem underhåller det?

UtvecklareAPI-200
KategoriInfrastruktur
Stjärnor257
Källahttps://github.com/API-200/api200
Protocolsmcp

Regelefterlevnad

EU AI Act Risk ClassNot assessed
Compliance Score100/100
JurisdiktionsAssessed across 52 jurisdiktions

Populära alternativ inom 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 programvara 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-stjärnor. Nerq Trust Score: 63/100 (C).

Nerq independently analyzes every programvara, app, and extension across multiple trust signals including säkerhet vulnerabilities, underhåll activity, license regelefterlevnad, and communityanvändning.

How Nerq Assesses Api200's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensioner. Here is how Api200 performs in each:

The overall Trust Score 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 säkerhet 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 programvara:

  1. Check the source code — Granska repository säkerhet policy, open issues, and recent commits for signs of active underhåll.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Api200's dependency tree.
  3. Recension 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. Granska 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 säkerhet 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. Granska tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency säkerhet

Check Api200's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher säkerhet risk.

Update frequency

Regularly check for updates to Api200. Säkerhet 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 regelefterlevnad

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 regelefterlevnad with your säkerhet policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for säkerhet advisories

Subscribe to Api200's säkerhet 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's trust score of 62.9/100 meets your organization's risk tolerance. We recommend running a manual säkerhet assessment alongside the automated Nerq score.

How Api200 Compares to Industry Standards

Nerq indexes over 6 million programvaras, apps, and packages across dozens of categories. Among infrastructure tools, the average Trust Score 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 dimensioner.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks måttlig 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 Api200 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 underhåll 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 säkerhet and quality. Conversely, a downward trend may signal reduced underhåll, 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 — säkerhet, underhåll, dokumentation, regelefterlevnad, and community — has evolved independently, providing granular visibility into which aspects of Api200 are strengthening or weakening over time.

Api200 vs Alternativ

In the infrastructure category, Api200 scores 62.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Viktigaste slutsatser

Vanliga frågor

Är Api200 säker?
Använd med viss försiktighet. api200 med ett Nerq-förtroendepoäng på 62.9/100 (C). Starkaste signalen: regelefterlevnad (100/100). Poäng baserad på Underhåll (0/100), Popularitet (1/100), Dokumentation (0/100).
Vad är Api200s förtroendepoäng?
api200: 62.9/100 (C). Poäng baserad på Underhåll (0/100), Popularitet (1/100), Dokumentation (0/100). Compliance: 100/100. Poäng uppdateras när ny data finns tillgänglig. API: GET nerq.ai/v1/preflight?target=api200
Vilka är säkrare alternativ till Api200?
I kategorin Infrastruktur, higher-rated alternatives include n8n-io/n8n (78/100), langflow-ai/langflow (88/100), langgenius/dify (79/100). api200 scores 62.9/100.
Hur ofta uppdateras Api200s säkerhetspoäng?
Nerq continuously monitors Api200 and updates its trust score as new data becomes available. Current: 62.9/100 (C), last verifierad 2026-04-08. API: GET nerq.ai/v1/preflight?target=api200
Kan jag använda Api200 i en reglerad miljö?
Api200 har inte nått Nerqs verifieringsgräns på 70. Ytterligare granskning rekommenderas.
API: /v1/preflight Trust Badge API Docs

Se även

Disclaimer: Nerqs förtroendepoäng är automatiserade bedömningar baserade på offentligt tillgängliga signaler. De utgör inte rekommendationer eller garantier. Gör alltid din egen verifiering.

Vi använder cookies för analys och cachelagring. Integritet