Er Any Openapi sikker?

Any Openapi — Nerq Tillidsscore 47.4/100 (Karakter D). Baseret på analyse af 3 tillidsdimensioner vurderes det som har bemærkelsesværdige sikkerhedsproblemer. Sidst opdateret: 2026-04-01.

Vær forsigtig med Any Openapi. Any Openapi is a software tool with a Nerq Tillidsscore of 47.4/100 (D), based on 3 independent data dimensions. Det er under den anbefalede tærskel på 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Maskinlæsbare data (JSON).

Er Any Openapi sikker?

NEJ — BRUG MED FORSIGTIGHED — Any Openapi has a Nerq Tillidsscore of 47.4/100 (D). Har under gennemsnitlige tillidssignaler med betydelige huller i sikkerhed, vedligeholdelse eller dokumentation. Anbefales ikke til produktionsbrug uden grundig manuel gennemgang og yderligere sikkerhedsforanstaltninger.

Sikkerhedsanalyse → {name} privatlivsrapport →

Hvad er Any Openapis tillidsscore?

Any Openapi has a Nerq Tillidsscore of 47.4/100, earning a D grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.

Vedligeholdelse
0
Dokumentation
0
Popularitet
0

Hvad er de vigtigste sikkerhedsresultater for Any Openapi?

Any Openapi's strongest signal is vedligeholdelse at 0/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Maintenance: 0/100 — low maintenance activity
Documentation: 0/100 — limited documentation
Popularity: 0/100 — 80 stars on pulsemcp

Hvad er Any Openapi og hvem vedligeholder det?

Udviklerhttps://github.com/baryhuang/mcp-server-any-openapi
Kategoriapi|integration
Stjerner80
Kildehttps://github.com/baryhuang/mcp-server-any-openapi

Populære alternativer i api|integration

X
44.7/100 · E
pulsemcp
Haoka API
43.2/100 · E
pulsemcp
Memberkit
43.4/100 · E
pulsemcp
api-agent
48.8/100 · D
pypi_full

What Is Any Openapi?

Any Openapi is a software tool in the api|integration category: Integrates with any OpenAPI-compliant service using dynamic tool generation and vector-based semantic search.. It has 80 GitHub stars. Nerq Tillidsscore: 47/100 (D).

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 Any Openapi's Safety

Nerq's Tillidsscore is calculated from 13+ independent signals aggregated into five dimensions. Here is how Any Openapi performs in each:

The overall Tillidsscore of 47.4/100 (D) 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 Any Openapi?

Any Openapi is designed for:

Risk guidance: We recommend caution with Any Openapi. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Any Openapi'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 Any Openapi's dependency tree.
  3. Anmeldelse permissions — Understand what access Any Openapi requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Any Openapi 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=Any OpenAPI
  6. Gennemgå license — Confirm that Any Openapi'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 Any Openapi

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

Data handling

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

Update frequency

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

Third-party integrations

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

Best Practices for Using Any Openapi Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Any Openapi?

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

tillidsscore for

For each scenario, evaluate whether Any Openapi 47.4/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Any Openapi Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among api|integration tools, the average Tillidsscore is 62/100. Any Openapi's score of 47.4/100 is below the category average of 62/100.

This suggests that Any Openapi trails behind many comparable api|integration tools. Organizations with strict security 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 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.

Tillidsscore History

Nerq continuously monitors Any Openapi and recalculates its Tillidsscore 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, Any Openapi'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 Any Openapi's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Any OpenAPI&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 Any Openapi are strengthening or weakening over time.

Any Openapi vs Alternatives

In the api|integration category, Any Openapi scorer 47.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Vigtigste pointer

Ofte stillede spørgsmål

Er Any Openapi sikker at bruge?
Vær forsigtig. Any OpenAPI has a Nerq Tillidsscore of 47.4/100 (D). Stærkeste signal: vedligeholdelse (0/100). Score baseret på maintenance (0/100), popularity (0/100), documentation (0/100).
Hvad er tillidsscoren for Any Openapi?
Any OpenAPI: 47.4/100 (D). Score baseret på: maintenance (0/100), popularity (0/100), documentation (0/100). Scorer opdateres, efterhånden som nye data bliver tilgængelige. API: GET nerq.ai/v1/preflight?target=Any OpenAPI
Hvad er sikrere alternativer til Any Openapi?
In the api|integration category, højere rangerede alternativer inkluderer X (45/100), Haoka API (43/100), Memberkit (43/100). Any OpenAPI scorer 47.4/100.
How often is Any Openapi's safety score updated?
Nerq continuously monitors Any Openapi 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: 47.4/100 (D), last verified 2026-04-01. API: GET nerq.ai/v1/preflight?target=Any OpenAPI
Kan jeg bruge Any Openapi i et reguleret miljø?
Any Openapi 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: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.

We use cookies for analytics and caching. Privatliv Policy