Er Zhangdi trygt?
Zhangdi — Nerq Trust Score 42.4/100 (Karakter E). Poeng basert på 3 independent trust signals.
Zhangdi er en software tool har en Nerq-tillitspoeng på 42.4/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 Zhangdi trygt?
Tillitspoeng detaljer — Zhangdi har en Nerq-tillitspoeng på 42.4/100 (E). Measured across 3 independent trust signals.
Hva er tillitspoengene til Zhangdi?
Zhangdi har en Nerq-tillitspoeng på 42.4/100 med karakteren E. Denne poengsummen er basert på 3 uavhengig målte dimensjoner, inkludert sikkerhet, vedlikehold og samfunnsadopsjon.
Hva er de viktigste sikkerhetsfunnene for Zhangdi?
Zhangdis sterkeste signal er vedlikehold på 0/100. Ingen kjente sårbarheter er funnet.
Hva er Zhangdi og hvem vedlikeholder det?
| Utvikler | 0x3c7d5bb537abae440e0abe552342f422a4b1e6c1 |
| Kategori | Infrastructure |
| Stjerner | 1 |
| Kilde | https://8004scan.io/agents/zhangdi |
| Protocols | x402 |
Populære alternativer i infrastructure
What Is Zhangdi?
Zhangdi is a software tool in the infrastructure category: A professional AI agent for business intelligence, specializing in advanced data analysis, generation of visual charts, and automated report creation, especially in the fields of Crypto and DeFi. Core functions: - Deep data analysis: Supports CSV, JSON, and SQL database imports, and performs comple. It has 1 GitHub stars. Nerq Trust Score: 42/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 Zhangdi's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensjoner. Here is how Zhangdi performs in each:
- Vedlikehold (0/100): Zhangdi 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 dokumentasjon, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Basert på GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 42.4/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 Zhangdi?
Zhangdi is commonly evaluated by:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Zhangdi'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 Zhangdi's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Gjennomgå repository sikkerhet policy, open issues, and recent commits for signs of active vedlikehold.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for kjente sårbarheter in Zhangdi's dependency tree. - Anmeldelse permissions — Understand what access Zhangdi requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Zhangdi 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=zhangdi - Gjennomgå license — Confirm that Zhangdi'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 sikkerhet concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Zhangdi
When evaluating whether Zhangdi is safe, consider these category-specific risks:
Understand how Zhangdi processes, stores, and transmits your data. Gjennomgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Zhangdi's dependency tree for kjente sårbarheter. Tools with outdated or unmaintained dependencies pose a higher sikkerhet risk.
Regularly check for updates to Zhangdi. Sikkerhet patches and bug fixes are only effective if you're running the latest version.
If Zhangdi 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 Zhangdi's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Zhangdi in violation of its license can expose your organization to legal liability.
Best Practices for Using Zhangdi Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Zhangdi while minimizing risk:
Periodically review how Zhangdi is used in your workflow. Check for unexpected behavior, permissions drift, and samsvar with your sikkerhet policies.
Ensure Zhangdi and all its dependencies are running the latest stable versions to benefit from sikkerhet patches.
Grant Zhangdi only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Zhangdi's sikkerhet advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Zhangdi is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Zhangdi
Nerq's signals are one input. In the following situations, evaluate Zhangdi'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 Zhangdi's measured trust score of 42.4/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Zhangdi is suitable for any particular use.
How Zhangdi 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. Zhangdi's score of 42.4/100 is below the category average of 62/100.
This suggests that Zhangdi 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 Zhangdi 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, Zhangdi'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 Zhangdi's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=zhangdi&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 Zhangdi are strengthening or weakening over time.
Zhangdi vs Alternativer
In the infrastructure category, Zhangdi scores 42.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Zhangdi vs n8n — Trust Score: 69.1/100
- Zhangdi vs langflow — Trust Score: 77.0/100
- Zhangdi vs dify — Trust Score: 69.7/100
Viktigste punkter
- Zhangdi has a measured Nerq Trust Score of 42.4/100 (E) — a composite of independent signals, not a suitability judgment.
- Among infrastructure tools, Zhangdi scores below the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — sikkerhet, vedlikehold, dokumentasjon, samsvar, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Ofte stilte spørsmål
Er Zhangdi trygt?
Hva er tillitspoengene til Zhangdi?
Hva er tryggere alternativer til Zhangdi?
Hvor ofte oppdateres Zhangdis sikkerhetspoeng?
Kan jeg bruke Zhangdi i et regulert miljø?
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.