Er Dataiku Oauth trygt?

Dataiku Oauth — Nerq Trust Score 40.0/100 (Karakter E). Poeng basert på 3 independent trust signals.

Dataiku Oauth er en software tool har en Nerq-tillitspoeng på 40.0/100 (E), based on 3 uavhengige datadimensjoner. Vedlikehold: 0/100. Popularitet: 0/100. Data hentet fra flere offentlige kilder inkludert pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sist oppdatert: n/a. Maskinlesbare data (JSON).

Er Dataiku Oauth trygt?

Tillitspoeng detaljer — Dataiku Oauth har en Nerq-tillitspoeng på 40.0/100 (E). Measured across 3 independent trust signals.

Sikkerhetsanalyse → Dataiku Oauth personvernrapport →

Hva er tillitspoengene til Dataiku Oauth?

Dataiku Oauth har en Nerq-tillitspoeng på 40.0/100 med karakteren E. Denne poengsummen er basert på 3 uavhengig målte dimensjoner, inkludert sikkerhet, vedlikehold og samfunnsadopsjon.

Vedlikehold
0
Dokumentasjon
0
Popularitet
0

Hva er de viktigste sikkerhetsfunnene for Dataiku Oauth?

Dataiku Oauths sterkeste signal er vedlikehold på 0/100. Ingen kjente sårbarheter er funnet.

⚠Vedlikehold: 0/100 — lav vedlikeholdsaktivitet
⚠Dokumentasjon: 0/100 — begrenset dokumentasjon
⚠Popularitet: 0/100 — 1 stjerner på pulsemcp

Hva er Dataiku Oauth og hvem vedlikeholder det?

Utviklerhttps://github.com/jediv/mcp-oauth-server
KategoriInfrastructure
Stjerner1
Kildehttps://github.com/jediv/mcp-oauth-server

Populære alternativer i infrastructure

n8n-io/n8n
69.1/100 · C
github
langflow-ai/langflow
77.0/100 · B
github
langgenius/dify
69.7/100 · C
github
open-webui/open-webui
60.4/100 · C
github
google-gemini/gemini-cli
56.2/100 · D
github

What Is Dataiku Oauth?

Dataiku Oauth is a software tool in the infrastructure category: Dataiku webapp that exposes agent tools as OAuth 2.1-secured MCP servers with multi-server support.. It has 1 GitHub stars. Nerq Trust Score: 40/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhet vulnerabilities, vedlikehold activity, license samsvar, and fellesskapsadopsjon.

How Nerq Assesses Dataiku Oauth's Safety

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

The overall Trust Score of 40.0/100 (E) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.

Who Typically Evaluates Dataiku Oauth?

Dataiku Oauth is commonly evaluated by:

How to read the signals: Dataiku Oauth's measured signals (vedlikehold 0/100, dokumentasjon 0/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.

How to Verify Dataiku Oauth's Safety Yourself

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

  1. Check the source code — Gjennomgå repository sikkerhet policy, open issues, and recent commits for signs of active vedlikehold.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for kjente sårbarheter in Dataiku Oauth's dependency tree.
  3. Anmeldelse permissions — Understand what access Dataiku Oauth requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Dataiku Oauth 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=Dataiku OAuth
  6. Gjennomgå license — Confirm that Dataiku Oauth'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 sikkerhet concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Dataiku Oauth

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

Data handling

Understand how Dataiku Oauth processes, stores, and transmits your data. Gjennomgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sikkerhet

Check Dataiku Oauth's dependency tree for kjente sårbarheter. Tools with outdated or unmaintained dependencies pose a higher sikkerhet risk.

Update frequency

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

Third-party integrations

If Dataiku Oauth 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 samsvar

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

Best Practices for Using Dataiku Oauth Safely

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

Conduct regular audits

Periodically review how Dataiku Oauth is used in your workflow. Check for unexpected behavior, permissions drift, and samsvar with your sikkerhet policies.

Keep dependencies updated

Ensure Dataiku Oauth and all its dependencies are running the latest stable versions to benefit from sikkerhet patches.

Follow least privilege

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

Monitor for sikkerhet advisories

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

Situations That Warrant Independent Review of Dataiku Oauth

Nerq's signals are one input. In the following situations, evaluate Dataiku Oauth's measured signals against your own requirements before making a decision:

For each situation, compare Dataiku Oauth's measured trust score of 40.0/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Dataiku Oauth is suitable for any particular use.

How Dataiku Oauth Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average Trust Score is 62/100. Dataiku Oauth's score of 40.0/100 is below the category average of 62/100.

This suggests that Dataiku Oauth trails behind many comparable infrastructure tools. Organizations with strict sikkerhet 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 moderat 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 Dataiku Oauth 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 vedlikehold patterns change, Dataiku Oauth'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 sikkerhet and quality. Conversely, a downward trend may signal reduced vedlikehold, growing technical debt, or unresolved vulnerabilities. To track Dataiku Oauth's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Dataiku OAuth&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 — sikkerhet, vedlikehold, dokumentasjon, samsvar, and community — has evolved independently, providing granular visibility into which aspects of Dataiku Oauth are strengthening or weakening over time.

Dataiku Oauth vs Alternativer

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

Viktigste punkter

Ofte stilte spørsmål

Er Dataiku Oauth trygt?
Dataiku OAuth har en Nerq-tillitspoeng på 40.0/100 (E). Sterkeste signal: vedlikehold (0/100). Poeng basert på Vedlikehold (0/100), Popularitet (0/100), Dokumentasjon (0/100).
Hva er tillitspoengene til Dataiku Oauth?
Dataiku OAuth: 40.0/100 (E). Poeng basert på Vedlikehold (0/100), Popularitet (0/100), Dokumentasjon (0/100). Poeng oppdateres når nye data er tilgjengelige. API: GET nerq.ai/v1/preflight?target=Dataiku OAuth
Hva er tryggere alternativer til Dataiku Oauth?
I kategorien Infrastructure, higher-rated alternatives include n8n-io/n8n (69/100), langflow-ai/langflow (77/100), langgenius/dify (70/100). Dataiku OAuth scores 40.0/100.
Hvor ofte oppdateres Dataiku Oauths sikkerhetspoeng?
Nerq recomputes Dataiku Oauth's trust score as new data becomes available. Current: 40.0/100 (E). API: GET nerq.ai/v1/preflight?target=Dataiku OAuth
Kan jeg bruke Dataiku Oauth i et regulert miljø?
Dataiku Oauth: 40.0/100 (E). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Se også

Disclaimer: Nerqs tillitspoeng er automatiserte vurderinger basert på offentlig tilgjengelige signaler. De utgjør ikke anbefalinger eller garantier. Utfør alltid din egen verifisering.

Vi bruker informasjonskapsler for analyse og hurtiglagring. Personvern