Is Tigris veilig?
Tigris — Nerq Trust Score 55.4/100 (D-beoordeling). Score gebaseerd op 5 independent trust signals.
Tigris is een software tool met een Nerq Vertrouwensscore van 55.4/100 (D), based on 5 onafhankelijke gegevensdimensies. Beveiliging: 0/100. Onderhoud: 0/100. Populariteit: 0/100. Gegevens afkomstig van meerdere openbare bronnen waaronder pakketregisters, GitHub, NVD, OSV.dev en OpenSSF Scorecard. Laatst bijgewerkt: n/a. Machineleesbare gegevens (JSON).
Is Tigris veilig?
Vertrouwensscore details — Tigris has a Nerq Trust Score of 55.4/100 (D). Measured across 5 independent trust signals.
Wat is de vertrouwensscore van Tigris?
Tigris heeft een Nerq Trust Score van 55.4/100 met het cijfer D. Deze score is gebaseerd op 5 onafhankelijk gemeten dimensies, waaronder beveiliging, onderhoud en community-adoptie.
Wat zijn de belangrijkste beveiligingsbevindingen voor Tigris?
Het sterkste signaal van Tigris is naleving met 100/100. Er zijn geen bekende kwetsbaarheden gedetecteerd.
Wat is Tigris en wie onderhoudt het?
| Ontwikkelaar | mcp |
| Categorie | Uncategorized |
| Bron | https://hub.docker.com/r/mcp/tigris |
| Protocols | docker |
Naleving van regelgeving
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdicties |
What Is Tigris?
Tigris is a software tool in the uncategorized category: Tigris is a globally distributed S3-compatible object storage service that provides low latency a.... Nerq Trust Score: 55/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.
How Nerq Assesses Tigris's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensies. Here is how Tigris performs in each:
- Beveiliging (0/100): Tigris's beveiliging posture is poor. This score factors in known CVEs, dependency vulnerabilities, beveiliging policy presence, and code signing practices.
- Onderhoud (0/100): Tigris is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API documentatie, usage examples, and contribution guidelines.
- Compliance (100/100): Tigris is broadly compliant. Assessed against regulations in 52 jurisdicties including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Gebaseerd op GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 55.4/100 (D) 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 Tigris?
Tigris is commonly evaluated by:
- Developers and teams working with uncategorized tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Tigris's measured signals (beveiliging 0/100, onderhoud 0/100, documentatie 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 Tigris's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Bekijk de repository beveiliging policy, open issues, and recent commits for signs of active onderhoud.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Tigris's dependency tree. - Beoordeling permissions — Understand what access Tigris requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Tigris in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=tigris - Bekijk de license — Confirm that Tigris'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.
- 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 beveiliging concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Tigris
When evaluating whether Tigris is safe, consider these category-specific risks:
Understand how Tigris processes, stores, and transmits your data. Bekijk de tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Tigris's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher beveiliging risk.
Regularly check for updates to Tigris. Beveiliging patches and bug fixes are only effective if you're running the latest version.
If Tigris 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.
Verify that Tigris's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Tigris in violation of its license can expose your organization to legal liability.
Best Practices for Using Tigris Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Tigris while minimizing risk:
Periodically review how Tigris is used in your workflow. Check for unexpected behavior, permissions drift, and naleving with your beveiliging policies.
Ensure Tigris and all its dependencies are running the latest stable versions to benefit from beveiliging patches.
Grant Tigris only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Tigris's beveiliging advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Tigris is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Tigris
Nerq's signals are one input. In the following situations, evaluate Tigris's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Tigris's measured trust score of 55.4/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Tigris is suitable for any particular use.
How Tigris Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Tigris's score of 55.4/100 is near the category average of 62/100.
This places Tigris in line with the typical uncategorized tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks matig 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 Tigris 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 onderhoud patterns change, Tigris'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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, growing technical debt, or unresolved vulnerabilities. To track Tigris's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=tigris&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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Tigris are strengthening or weakening over time.
Belangrijkste conclusies
- Tigris has a measured Nerq Trust Score of 55.4/100 (D) — a composite of independent signals, not a suitability judgment.
- Among uncategorized tools, Tigris scores near the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — beveiliging, onderhoud, documentatie, naleving, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Veelgestelde vragen
Is Tigris veilig?
Wat is de vertrouwensscore van Tigris?
Wat zijn veiligere alternatieven voor Tigris?
Hoe vaak wordt de beveiligingsscore van Tigris bijgewerkt?
Kan ik Tigris gebruiken in een gereguleerde omgeving?
Zie ook
Disclaimer: Nerq-vertrouwensscores zijn geautomatiseerde beoordelingen op basis van openbaar beschikbare signalen. Ze vormen geen aanbeveling of garantie. Voer altijd uw eigen verificatie uit.