Je Feishu Doc bezpečný?
Feishu Doc — Nerq Trust Score 36.5/100 (Stupeň E). Skóre založeno na 5 independent trust signals.
Feishu Doc je software tool se skóre důvěryhodnosti Nerq 36.5/100 (E). Data pocházejí z více veřejných zdrojů včetně registrů balíčků, GitHubu, NVD, OSV.dev a OpenSSF Scorecard. Naposledy aktualizováno: n/a. Strojově čitelná data (JSON).
Je Feishu Doc bezpečný?
Rozpis skóre důvěryhodnosti — Feishu Doc has a Nerq Trust Score of 36.5/100 (E). Measured across 1 independent trust signal.
Jaké je skóre důvěryhodnosti Feishu Doc?
Feishu Doc má Nerq skóre důvěryhodnosti 36.5/100 se stupněm E. Toto skóre je založeno na 5 nezávisle měřených dimenzích.
Jaká jsou klíčová bezpečnostní zjištění pro Feishu Doc?
Nejsilnější signál Feishu Doc je celková důvěryhodnost na 36.5/100. Nebyly zjištěny žádné známé zranitelnosti.
Co je Feishu Doc a kdo jej spravuje?
| Autor | https://github.com/shackleslay/feishu-doc-mcp |
| Kategorie | Uncategorized |
| Zdroj | https://github.com/shackleslay/feishu-doc-mcp |
What Is Feishu Doc?
Feishu Doc is a software tool in the uncategorized category: Feishu (Lark) cloud document operations with OAuth authentication and MCP gateway proxy.. Nerq Trust Score: 36/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bezpečnost vulnerabilities, údržba activity, license shoda, and přijetí komunitou.
How Nerq Assesses Feishu Doc's Safety
Nerq evaluates every software tool across 13+ independent trust signals drawn from public sources including GitHub, NVD, OSV.dev, OpenSSF Scorecard, and package registries. These signals are grouped into five core dimenzích: Bezpečnost (known CVEs, dependency vulnerabilities, bezpečnost policies), Údržba (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 jurisdictions), and Community (stars, forks, downloads, ecosystem integrations).
Feishu Doc receives an overall Trust Score of 36.5/100 (E). This is a measured composite, not a suitability judgment.
Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=Feishu Doc
Each dimension is weighted according to its importance for the tool's category. For example, Bezpečnost and Údržba carry higher weight for tools that handle sensitive data or execute code, while Community and Documentation are weighted more heavily for developer-facing libraries and frameworks. This ensures that Feishu Doc's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five dimenzích, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).
Who Typically Evaluates Feishu Doc?
Feishu Doc 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: Feishu Doc's measured signals (the trust signals above) 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 Feishu Doc's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Zkontrolujte repository bezpečnost policy, open issues, and recent commits for signs of active údržba.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Feishu Doc's dependency tree. - Recenze permissions — Understand what access Feishu Doc requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Feishu Doc 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=Feishu Doc - Zkontrolujte license — Confirm that Feishu Doc'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 bezpečnost concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Feishu Doc
When evaluating whether Feishu Doc is safe, consider these category-specific risks:
Understand how Feishu Doc processes, stores, and transmits your data. Zkontrolujte tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Feishu Doc's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpečnost risk.
Regularly check for updates to Feishu Doc. Bezpečnost patches and bug fixes are only effective if you're running the latest version.
If Feishu Doc 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 Feishu Doc's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Feishu Doc in violation of its license can expose your organization to legal liability.
Best Practices for Using Feishu Doc Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Feishu Doc while minimizing risk:
Periodically review how Feishu Doc is used in your workflow. Check for unexpected behavior, permissions drift, and shoda with your bezpečnost policies.
Ensure Feishu Doc and all its dependencies are running the latest stable versions to benefit from bezpečnost patches.
Grant Feishu Doc only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Feishu Doc's bezpečnost advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Feishu Doc is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Feishu Doc
Nerq's signals are one input. In the following situations, evaluate Feishu Doc'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 Feishu Doc's measured trust score of 36.5/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Feishu Doc is suitable for any particular use.
How Feishu Doc 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. Feishu Doc's score of 36.5/100 is below the category average of 62/100.
This suggests that Feishu Doc trails behind many comparable uncategorized tools. Organizations with strict bezpečnost 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 střední 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 Feishu Doc 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 údržba patterns change, Feishu Doc'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 bezpečnost and quality. Conversely, a downward trend may signal reduced údržba, growing technical debt, or unresolved vulnerabilities. To track Feishu Doc's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Feishu Doc&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 — bezpečnost, údržba, dokumentace, shoda, and community — has evolved independently, providing granular visibility into which aspects of Feishu Doc are strengthening or weakening over time.
Hlavní závěry
- Feishu Doc has a measured Nerq Trust Score of 36.5/100 (E) — a composite of independent signals, not a suitability judgment.
- Among uncategorized tools, Feishu Doc scores below the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — bezpečnost, údržba, dokumentace, shoda, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Často kladené otázky
Je Feishu Doc bezpečný?
Jaké je skóre důvěryhodnosti Feishu Doc?
Jaké jsou bezpečnější alternativy k Feishu Doc?
Jak často se aktualizuje bezpečnostní skóre Feishu Doc?
Mohu používat Feishu Doc v regulovaném prostředí?
Viz také
Disclaimer: Skóre důvěryhodnosti Nerq jsou automatizovaná hodnocení založená na veřejně dostupných signálech. Nejsou doporučením ani zárukou. Vždy proveďte vlastní ověření.