Stream Presenceは安全ですか?
Stream Presence — Nerq Trust Score 59.0/100 (Cグレード). スコアの基準: 5 independent trust signals.
Stream Presence はsoftware toolです Nerq信頼スコア59.0/100(C). データソース: パッケージレジストリ、GitHub、NVD、OSV.dev、OpenSSF Scorecardを含む複数の公開ソース. 最終更新: n/a. 機械可読データ(JSON).
Stream Presenceは安全ですか?
信頼スコアの内訳 — Stream Presence has a Nerq Trust Score of 59.0/100 (C). Measured across 1 independent trust signal.
Stream Presenceの信頼スコアは?
Stream PresenceのNerq信頼スコアは59.0/100で、Cグレードです。このスコアはセキュリティ、メンテナンス、コミュニティ採用を含む5の独立した次元に基づいています。
Stream Presenceの主なセキュリティ調査結果は?
Stream Presenceの最も強いシグナルは総合信頼度で59.0/100です。 既知の脆弱性は検出されていません。
Stream Presenceとは何で、誰が管理していますか?
| 作者 | 2f27cdefd1f550403d1810df236defad3ff8f74bc4bcf171 |
| カテゴリ | Community |
| Source | https://agentverse.ai/agents/stream-presence |
communityの人気の代替品
What Is Stream Presence?
Stream Presence is a software tool in the community category: Signed proof-of-work receipts for AI agents: every job signed by the agent that did it, countersigned by the receiver, in a public ledger anyone can verify. First verification free.. Nerq Trust Score: 59/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.
How Nerq Assesses Stream Presence'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 次元: セキュリティ (known CVEs, dependency vulnerabilities, セキュリティ policies), メンテナンス (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).
Stream Presence receives an overall Trust Score of 59.0/100 (C). 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=Stream Presence
Each dimension is weighted according to its importance for the tool's category. For example, セキュリティ and メンテナンス 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 Stream Presence's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five 次元, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).
Who Typically Evaluates Stream Presence?
Stream Presence is commonly evaluated by:
- Developers and teams working with community tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Stream Presence'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 Stream Presence's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — 確認してください repository セキュリティ policy, open issues, and recent commits for signs of active メンテナンス.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Stream Presence's dependency tree. - レビュー permissions — Understand what access Stream Presence requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Stream Presence 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=Stream Presence - 確認してください license — Confirm that Stream Presence'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 セキュリティ concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Stream Presence
When evaluating whether Stream Presence is safe, consider these category-specific risks:
Understand how Stream Presence processes, stores, and transmits your data. 確認してください tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Stream Presence's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher セキュリティ risk.
Regularly check for updates to Stream Presence. セキュリティ patches and bug fixes are only effective if you're running the latest version.
If Stream Presence 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 Stream Presence's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Stream Presence in violation of its license can expose your organization to legal liability.
Best Practices for Using Stream Presence Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Stream Presence while minimizing risk:
Periodically review how Stream Presence is used in your workflow. Check for unexpected behavior, permissions drift, and コンプライアンス with your セキュリティ policies.
Ensure Stream Presence and all its dependencies are running the latest stable versions to benefit from セキュリティ patches.
Grant Stream Presence only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Stream Presence's セキュリティ advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Stream Presence is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Stream Presence
Nerq's signals are one input. In the following situations, evaluate Stream Presence'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 Stream Presence's measured trust score of 59.0/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Stream Presence is suitable for any particular use.
How Stream Presence Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among community tools, the average Trust Score is 62/100. Stream Presence's score of 59.0/100 is near the category average of 62/100.
This places Stream Presence in line with the typical community 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 Stream Presence 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, Stream Presence'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 Stream Presence's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Stream Presence&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 Stream Presence are strengthening or weakening over time.
Stream Presence vs 代替品
In the community category, Stream Presence scores 59.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Stream Presence vs WritersLogic Business Agents — Trust Score: 64.0/100
- Stream Presence vs WritersLogic Developer Agents — Trust Score: 64.0/100
- Stream Presence vs WritersLogic Agent インフラストラクチャ — Trust Score: 64.0/100
重要なポイント
- Stream Presence has a measured Nerq Trust Score of 59.0/100 (C) — a composite of independent signals, not a suitability judgment.
- Among community tools, Stream Presence scores near the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — セキュリティ, メンテナンス, ドキュメント, コンプライアンス, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
よくある質問
Stream Presenceは安全ですか?
Stream Presenceの信頼スコアは?
Stream Presenceのより安全な代替は何ですか?
Stream Presenceの安全性スコアはどのくらいの頻度で更新されますか?
規制環境でStream Presenceを使用できますか?
関連項目
Disclaimer: Nerqの信頼スコアは、公開されている情報に基づく自動評価です。推奨や保証ではありません。必ずご自身でも確認してください。