Je Sceneview bezpečný?

Sceneview — Nerq Trust Score 65.2/100 (Stupeň B-). Na základě analýzy 5 dimenzí důvěryhodnosti je obecně bezpečný, ale s některými obavami. Naposledy aktualizováno: 2026-05-01.

Používejte Sceneview s opatrností. Sceneview je software tool se skóre důvěryhodnosti Nerq 65.2/100 (B-). Pod ověřeným prahem Nerq 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: 2026-05-01. Strojově čitelná data (JSON).

Je Sceneview bezpečný?

CAUTION — Sceneview has a Nerq Trust Score of 65.2/100 (B-). Má střední signály důvěryhodnosti, ale vykazuje některé oblasti k pozornosti that warrant attention. Suitable for development use — review bezpečnost and údržba signals before production deployment.

Bezpečnostní analýza → Zpráva o soukromí Sceneview →

Jaké je skóre důvěryhodnosti Sceneview?

Sceneview má Nerq skóre důvěryhodnosti 65.2/100 se stupněm B-. Toto skóre je založeno na 5 nezávisle měřených dimenzích.

Celková důvěryhodnost
65.2

Jaká jsou klíčová bezpečnostní zjištění pro Sceneview?

Nejsilnější signál Sceneview je celková důvěryhodnost na 65.2/100. Nebyly zjištěny žádné známé zranitelnosti. Dosud nedosáhl ověřeného prahu Nerq 70+.

Souhrnné skóre důvěryhodnosti: 65.2/100 ze všech dostupných signálů

Co je Sceneview a kdo jej spravuje?

Autorhttps://github.com/SceneView/sceneview
KategorieUncategorized
Zdrojhttps://github.com/SceneView/sceneview

What Is Sceneview?

Sceneview is a software tool in the uncategorized category: 3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.. Nerq Trust Score: 65/100 (B-).

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 Sceneview'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).

Sceneview receives an overall Trust Score of 65.2/100 (B-), which Nerq considers střední. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=io.github.ThomasGorisse/sceneview

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 Sceneview'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 Should Use Sceneview?

Sceneview is designed for:

Risk guidance: Sceneview is suitable for development and testing environments. Before production deployment, conduct a thorough review of its bezpečnost posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify Sceneview's Safety Yourself

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

  1. Check the source code — Zkontrolujte repository bezpečnost policy, open issues, and recent commits for signs of active údržba.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Sceneview's dependency tree.
  3. Recenze permissions — Understand what access Sceneview requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Sceneview 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=io.github.ThomasGorisse/sceneview
  6. Zkontrolujte license — Confirm that Sceneview'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 bezpečnost concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Sceneview

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

Data handling

Understand how Sceneview processes, stores, and transmits your data. Zkontrolujte tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency bezpečnost

Check Sceneview's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpečnost risk.

Update frequency

Regularly check for updates to Sceneview. Bezpečnost patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Sceneview 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 shoda

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

Best Practices for Using Sceneview Safely

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

Conduct regular audits

Periodically review how Sceneview is used in your workflow. Check for unexpected behavior, permissions drift, and shoda with your bezpečnost policies.

Keep dependencies updated

Ensure Sceneview and all its dependencies are running the latest stable versions to benefit from bezpečnost patches.

Follow least privilege

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

Monitor for bezpečnost advisories

Subscribe to Sceneview's bezpečnost 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 Sceneview is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Sceneview?

Even promising tools aren't right for every situation. Consider avoiding Sceneview in these scenarios:

For each scenario, evaluate whether Sceneview's trust score of 65.2/100 meets your organization's risk tolerance. We recommend running a manual bezpečnost assessment alongside the automated Nerq score.

How Sceneview 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. Sceneview's score of 65.2/100 is above the category average of 62/100.

This positions Sceneview favorably among uncategorized tools. While it outperforms the average, there is still room for improvement in certain trust dimenzích.

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 Sceneview 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, Sceneview'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 Sceneview's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=io.github.ThomasGorisse/sceneview&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 Sceneview are strengthening or weakening over time.

Hlavní závěry

Jaká data Sceneview shromažďuje?

Soukromí assessment for Sceneview is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.

Je Sceneview bezpečný?

Bezpečnost score: v hodnocení. Review bezpečnost practices and consider alternatives with higher bezpečnost scores for sensitive use cases.

Nerq monitoruje tuto entitu oproti NVD, OSV.dev a databázím zranitelností specifickým pro registry pro průběžné bezpečnostní hodnocení.

Úplná analýza: Bezpečnostní zpráva Sceneview

Jak jsme vypočítali toto skóre

Sceneview's trust score of 65.2/100 (B-) je vypočítáno z více veřejných zdrojů včetně registrů balíčků, GitHubu, NVD, OSV.dev a OpenSSF Scorecard. Skóre odráží 0 nezávislých dimenzí: . Každá dimenze má stejnou váhu pro vytvoření souhrnného skóre důvěryhodnosti.

Nerq analyzuje více než 7,5 milionu entit ve 26 registrech pomocí stejné metodologie, což umožňuje přímé srovnání mezi entitami. Skóre jsou průběžně aktualizována, jakmile jsou k dispozici nová data.

Tato stránka byla naposledy zkontrolována May 01, 2026. Verze dat: 1.0.

Kompletní dokumentace metodologie · Strojově čitelná data (JSON API)

Často kladené otázky

Je Sceneview bezpečný?
Používejte s opatrností. io.github.ThomasGorisse/sceneview se skóre důvěryhodnosti Nerq 65.2/100 (B-). Nejsilnější signál: celková důvěryhodnost (65.2/100). Skóre založeno na multiple trust dimenzích.
Jaké je skóre důvěryhodnosti Sceneview?
io.github.ThomasGorisse/sceneview: 65.2/100 (B-). Skóre založeno na multiple trust dimenzích. Skóre se aktualizují, jakmile jsou k dispozici nová data. API: GET nerq.ai/v1/preflight?target=io.github.ThomasGorisse/sceneview
Jaké jsou bezpečnější alternativy k Sceneview?
V kategorii Uncategorized, další software tool se analyzují — zkontrolujte později. io.github.ThomasGorisse/sceneview scores 65.2/100.
Jak často se aktualizuje bezpečnostní skóre Sceneview?
Nerq continuously monitors Sceneview and updates its trust score as new data becomes available. Current: 65.2/100 (B-), last ověřeno 2026-05-01. API: GET nerq.ai/v1/preflight?target=io.github.ThomasGorisse/sceneview
Mohu používat Sceneview v regulovaném prostředí?
Sceneview nedosáhl prahu ověření Nerq 70. Doporučuje se dodatečné přezkoumání.
API: /v1/preflight Trust Badge API Docs

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í.

Používáme cookies pro analýzu a ukládání do mezipaměti. Soukromí