Inbox Zeroは安全ですか?

Inbox Zero — Nerq Trust Score 56.8/100 (Dグレード). スコアの基準: 5 independent trust signals.

Inbox Zero はsoftware toolです Nerq信頼スコア56.8/100(D), 5つの独立したデータ次元に基づく. セキュリティ: 0/100. メンテナンス: 0/100. 人気度: 0/100. データソース: パッケージレジストリ、GitHub、NVD、OSV.dev、OpenSSF Scorecardを含む複数の公開ソース. 最終更新: n/a. 機械可読データ(JSON).

Inbox Zeroは安全ですか?

信頼スコアの内訳 — Inbox Zero has a Nerq Trust Score of 56.8/100 (D). Measured across 5 independent trust signals.

セキュリティ分析 → プライバシーレポート →

Inbox Zeroの信頼スコアは?

Inbox ZeroのNerq信頼スコアは56.8/100で、Dグレードです。このスコアはセキュリティ、メンテナンス、コミュニティ採用を含む5の独立した次元に基づいています。

セキュリティ
0
Compliance
87
メンテナンス
0
ドキュメント
0
人気度
0

Inbox Zeroの主なセキュリティ調査結果は?

Inbox Zeroの最も強いシグナルはコンプライアンスで87/100です。 既知の脆弱性は検出されていません。

セキュリティスコア: 0/100 (弱い)
メンテナンス: 0/100 — メンテナンス活動が低い
Compliance: 87/100 — covers 45 of 52 jurisdictions
ドキュメント: 0/100 — 限定的な文書化
人気度: 0/100 — コミュニティ採用

Inbox Zeroとは何で、誰が管理していますか?

作者elie222
カテゴリUncategorized
Sourcehttps://hub.docker.com/r/elie222/inbox-zero
Protocolsdocker

規制コンプライアンス

EU AI Act Risk ClassNot assessed
Compliance Score87/100
JurisdictionsAssessed across 52 jurisdictions

Inbox Zeroの他プラットフォーム

他のレジストリでの同じ開発者/企業:

fsai
61/100 · npm
@alephmatic/kirimase
59/100 · npm
@inbox-zero/cli
54/100 · npm
@elie222/neo4jd3
46/100 · npm

What Is Inbox Zero?

Inbox Zero is a software tool in the uncategorized category: Inbox Zero - AI email assistant for Gmail and Outlook to reach inbox zero fast. Nerq Trust Score: 57/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.

How Nerq Assesses Inbox Zero's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 次元. Here is how Inbox Zero performs in each:

The overall Trust Score of 56.8/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 Inbox Zero?

Inbox Zero is commonly evaluated by:

How to read the signals: Inbox Zero's measured signals (セキュリティ 0/100, メンテナンス 0/100, ドキュメント 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 Inbox Zero's Safety Yourself

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

  1. Check the source code — 確認してください repository セキュリティ policy, open issues, and recent commits for signs of active メンテナンス.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Inbox Zero's dependency tree.
  3. レビュー permissions — Understand what access Inbox Zero requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Inbox Zero 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=inbox-zero
  6. 確認してください license — Confirm that Inbox Zero'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 セキュリティ concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Inbox Zero

When evaluating whether Inbox Zero is safe, consider these category-specific risks:

Data handling

Understand how Inbox Zero processes, stores, and transmits your data. 確認してください tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency セキュリティ

Check Inbox Zero's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher セキュリティ risk.

Update frequency

Regularly check for updates to Inbox Zero. セキュリティ patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Inbox Zero 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 コンプライアンス

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

Best Practices for Using Inbox Zero Safely

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

Conduct regular audits

Periodically review how Inbox Zero is used in your workflow. Check for unexpected behavior, permissions drift, and コンプライアンス with your セキュリティ policies.

Keep dependencies updated

Ensure Inbox Zero and all its dependencies are running the latest stable versions to benefit from セキュリティ patches.

Follow least privilege

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

Monitor for セキュリティ advisories

Subscribe to Inbox Zero's セキュリティ 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 Inbox Zero is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Inbox Zero

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

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

How Inbox Zero 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. Inbox Zero's score of 56.8/100 is near the category average of 62/100.

This places Inbox Zero 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 中程度 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 Inbox Zero 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 メンテナンス patterns change, Inbox Zero'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 セキュリティ and quality. Conversely, a downward trend may signal reduced メンテナンス, growing technical debt, or unresolved vulnerabilities. To track Inbox Zero's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=inbox-zero&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 — セキュリティ, メンテナンス, ドキュメント, コンプライアンス, and community — has evolved independently, providing granular visibility into which aspects of Inbox Zero are strengthening or weakening over time.

重要なポイント

よくある質問

Inbox Zeroは安全ですか?
inbox-zero Nerq信頼スコア56.8/100(D). 最も強いシグナル: コンプライアンス (87/100). スコアの基準: セキュリティ (0/100), メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100).
Inbox Zeroの信頼スコアは?
inbox-zero: 56.8/100 (D). スコアの基準: セキュリティ (0/100), メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100). Compliance: 87/100. 新しいデータが利用可能になるとスコアが更新さ���ます. API: GET nerq.ai/v1/preflight?target=inbox-zero
Inbox Zeroのより安全な代替は何ですか?
Uncategorizedカテゴリでは、 さらに多くのsoftware toolが分析中です — 後で確認してください。 inbox-zero scores 56.8/100.
Inbox Zeroの安全性スコアはどのくらいの頻度で更新されますか?
Nerq recomputes Inbox Zero's trust score as new data becomes available. Current: 56.8/100 (D). API: GET nerq.ai/v1/preflight?target=inbox-zero
規制環境でInbox Zeroを使用できますか?
Inbox Zero: 56.8/100 (D). Compliance: 45 of 52 jurisdictions. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

関連項目

Disclaimer: Nerqの信頼スコアは、公開されている情報に基づく自動評価です。推奨や保証ではありません。必ずご自身でも確認してください。

分析とキャッシュにCookieを使用しています。 プライバシー