Moneyclaw Pyは安全ですか?

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

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

Moneyclaw Pyは安全ですか?

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

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

Moneyclaw Pyの信頼スコアは?

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

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

Moneyclaw Pyの主なセキュリティ調査結果は?

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

⚠セキュリティスコア: 0/100 (弱い)
⚠メンテナンス: 1/100 — メンテナンス活動が低い
⚠Compliance: 82/100 — covers 42 of 52 jurisdictions
⚠ドキュメント: 1/100 — 限定的な文書化
⚠人気度: 0/100 — 44 スター( github

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

作者MindDock
カテゴリFinance
Stars44
Sourcehttps://github.com/MindDock/moneyclaw-py
Frameworksopenai · anthropic · ollama
Protocolsrest

規制コンプライアンス

EU AI Act Risk ClassMINIMAL
Compliance Score82/100
JurisdictionsAssessed across 52 jurisdictions

financeの人気の代替品

OpenBB-finance/OpenBB
69.3/100 · C
github
microsoft/qlib
81.8/100 · A
github
TauricResearch/TradingAgents
78.5/100 · B
github
TradingAgents-CN
72.7/100 · B
github
virattt/dexter
63.9/100 · C
github

What Is Moneyclaw Py?

Moneyclaw Py is a software tool in the finance category: 7x24 AI Agent for financial optimization and cost management.. It has 44 GitHubスター. Nerq Trust Score: 56/100 (D).

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

How Nerq Assesses Moneyclaw Py's Safety

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

The overall Trust Score of 55.9/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 Moneyclaw Py?

Moneyclaw Py is commonly evaluated by:

How to read the signals: Moneyclaw Py's measured signals (セキュリティ 0/100, メンテナンス 1/100, ドキュメント 1/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 Moneyclaw Py'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's セキュリティ 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 Moneyclaw Py's dependency tree.
  3. レビュー permissions — Understand what access Moneyclaw Py requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Moneyclaw Py 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=moneyclaw-py
  6. 確認してください license — Confirm that Moneyclaw Py'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 Moneyclaw Py

When evaluating whether Moneyclaw Py is safe, consider these category-specific risks:

Data handling

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

Dependency セキュリティ

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

Update frequency

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

Third-party integrations

If Moneyclaw Py 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 Moneyclaw Py's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Moneyclaw Py in violation of its license can expose your organization to legal liability.

Moneyclaw Py and the EU AI Act

Moneyclaw Py is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.

Nerq's コンプライアンス assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal コンプライアンス.

Best Practices for Using Moneyclaw Py Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for セキュリティ advisories

Subscribe to Moneyclaw Py'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 Moneyclaw Py is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Moneyclaw Py

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

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

How Moneyclaw Py Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among finance tools, the average Trust Score is 62/100. Moneyclaw Py's score of 55.9/100 is near the category average of 62/100.

This places Moneyclaw Py in line with the typical finance 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 Moneyclaw Py 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, Moneyclaw Py'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 Moneyclaw Py's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=moneyclaw-py&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 Moneyclaw Py are strengthening or weakening over time.

Moneyclaw Py vs 代替品

In the finance category, Moneyclaw Py scores 55.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:

重要なポイント

よくある質問

Moneyclaw Pyは安全ですか?
moneyclaw-py Nerq信頼スコア55.9/100(D). 最も強いシグナル: コンプライアンス (82/100). スコアの基準: セキュリティ (0/100), メンテナンス (1/100), 人気度 (0/100), ドキュメント (1/100).
Moneyclaw Pyの信頼スコアは?
moneyclaw-py: 55.9/100 (D). スコアの基準: セキュリティ (0/100), メンテナンス (1/100), 人気度 (0/100), ドキュメント (1/100). Compliance: 82/100. 新しいデータが利用可能になるとスコアが更新さ���ます. API: GET nerq.ai/v1/preflight?target=moneyclaw-py
Moneyclaw Pyのより安全な代替は何ですか?
Financeカテゴリでは、 higher-rated alternatives include OpenBB-finance/OpenBB (69/100), microsoft/qlib (82/100), TauricResearch/TradingAgents (78/100). moneyclaw-py scores 55.9/100.
Moneyclaw Pyの安全性スコアはどのくらいの頻度で更新されますか?
Nerq recomputes Moneyclaw Py's trust score as new data becomes available. Current: 55.9/100 (D). API: GET nerq.ai/v1/preflight?target=moneyclaw-py
規制環境でMoneyclaw Pyを使用できますか?
Moneyclaw Py: 55.9/100 (D). Compliance: 42 of 52 jurisdictions. EU AI Act compliant. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

関連項目

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

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