¿Es Source Freshdesk Seguro?
Source Freshdesk — Nerq Trust Score 59.9/100 (Grado D). Basado en el análisis de 5 dimensiones de confianza, se tiene preocupaciones de seguridad notables. Última actualización: 2026-04-08.
Usa Source Freshdesk con precaución. Source Freshdesk es un software tool con un Nerq Trust Score de 59.9/100 (D), basado en 5 dimensiones de datos independientes. Por debajo del umbral verificado de Nerq Seguridad: 0/100. Mantenimiento: 0/100. Popularidad: 0/100. Datos de múltiples fuentes públicas incluyendo registros de paquetes, GitHub, NVD, OSV.dev y OpenSSF Scorecard. Última actualización: 2026-04-08. Datos legibles por máquina (JSON).
¿Es Source Freshdesk Seguro?
CAUTION — Source Freshdesk has a Nerq Trust Score of 59.9/100 (D). Tiene señales de confianza moderadas pero muestra algunas áreas de preocupación that warrant attention. Suitable for development use — review seguridad and mantenimiento signals before production deployment.
¿Cuál es la puntuación de confianza de Source Freshdesk?
Source Freshdesk tiene una Puntuación de Confianza Nerq de 59.9/100, obteniendo un grado D. Esta puntuación se basa en 5 dimensiones medidas independientemente.
¿Cuáles son los hallazgos de seguridad clave de Source Freshdesk?
La señal más fuerte de Source Freshdesk es cumplimiento con 100/100. No se han detectado vulnerabilidades conocidas. Aún no ha alcanzado el umbral verificado de Nerq de 70+.
¿Qué es Source Freshdesk y quién lo mantiene?
| Autor | airbyte |
| Categoría | Uncategorized |
| Fuente | https://hub.docker.com/r/airbyte/source-freshdesk |
| Protocols | docker |
Cumplimiento Regulatorio
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Source Freshdesk en Otras Plataformas
Mismo desarrollador/empresa en otros registros:
What Is Source Freshdesk?
Source Freshdesk is a software tool in the uncategorized category available on docker_hub. Nerq Trust Score: 60/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including seguridad vulnerabilities, mantenimiento activity, license cumplimiento, and adopción por la comunidad.
How Nerq Assesses Source Freshdesk's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiones. Here is how Source Freshdesk performs in each:
- Seguridad (0/100): Source Freshdesk's seguridad posture is poor. This score factors in known CVEs, dependency vulnerabilities, seguridad policy presence, and code signing practices.
- Mantenimiento (0/100): Source Freshdesk 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 documentación, usage examples, and contribution guidelines.
- Compliance (100/100): Source Freshdesk is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Basado en GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 59.9/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 Source Freshdesk?
Source Freshdesk is designed for:
- Developers and teams working with uncategorized tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Source Freshdesk is suitable for development and testing environments. Before production deployment, conduct a thorough review of its seguridad posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.
How to Verify Source Freshdesk's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Revisar el/la repository seguridad policy, open issues, and recent commits for signs of active mantenimiento.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Source Freshdesk's dependency tree. - Reseña permissions — Understand what access Source Freshdesk requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Source Freshdesk 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=source-freshdesk - Revisar el/la license — Confirm that Source Freshdesk'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 seguridad concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Source Freshdesk
When evaluating whether Source Freshdesk is safe, consider these category-specific risks:
Understand how Source Freshdesk processes, stores, and transmits your data. Revisar el/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Source Freshdesk's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher seguridad risk.
Regularly check for updates to Source Freshdesk. Seguridad patches and bug fixes are only effective if you're running the latest version.
If Source Freshdesk 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 Source Freshdesk's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Source Freshdesk in violation of its license can expose your organization to legal liability.
Best Practices for Using Source Freshdesk Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Source Freshdesk while minimizing risk:
Periodically review how Source Freshdesk is used in your workflow. Check for unexpected behavior, permissions drift, and cumplimiento with your seguridad policies.
Ensure Source Freshdesk and all its dependencies are running the latest stable versions to benefit from seguridad patches.
Grant Source Freshdesk only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Source Freshdesk's seguridad advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Source Freshdesk is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Source Freshdesk?
Even promising tools aren't right for every situation. Consider avoiding Source Freshdesk in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional cumplimiento review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Source Freshdesk's trust score of 59.9/100 meets your organization's risk tolerance. We recommend running a manual seguridad assessment alongside the automated Nerq score.
How Source Freshdesk 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. Source Freshdesk's score of 59.9/100 is near the category average of 62/100.
This places Source Freshdesk 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 moderado 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 Source Freshdesk 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 mantenimiento patterns change, Source Freshdesk'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 seguridad and quality. Conversely, a downward trend may signal reduced mantenimiento, growing technical debt, or unresolved vulnerabilities. To track Source Freshdesk's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=source-freshdesk&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 — seguridad, mantenimiento, documentación, cumplimiento, and community — has evolved independently, providing granular visibility into which aspects of Source Freshdesk are strengthening or weakening over time.
Puntos Clave
- Source Freshdesk has a Trust Score of 59.9/100 (D) and is not yet Nerq Verified.
- Source Freshdesk shows moderado trust signals. Conduct thorough due diligence before deploying to production environments.
- Among uncategorized tools, Source Freshdesk scores near the category average of 62/100, suggesting room for improvement relative to peers.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Preguntas Frecuentes
¿Es Source Freshdesk Seguro?
¿Cuál es la puntuación de confianza de Source Freshdesk?
¿Cuáles son alternativas más seguras a Source Freshdesk?
¿Con qué frecuencia se actualiza la puntuación de Source Freshdesk?
¿Puedo usar Source Freshdesk en un entorno regulado?
Ver también
Disclaimer: Las puntuaciones de confianza de Nerq son evaluaciones automatizadas basadas en señales disponibles públicamente. No son respaldos ni garantías. Siempre realice su propia diligencia debida.