Ist Builder Vite sicher?

Builder Vite — Nerq Trust Score 62.8/100 (Note C). Basierend auf der Analyse von 1 Vertrauensdimensionen wird es als generell sicher, aber mit einigen Bedenken eingestuft. Zuletzt aktualisiert: 2026-04-09.

Verwende Builder Vite mit Vorsicht. Builder Vite ist ein software tool mit einem Nerq-Vertrauenswert von 62.8/100 (C), basierend auf 3 unabhängigen Datendimensionen. Unter der Nerq-Vertrauensschwelle Daten von mehreren öffentlichen Quellen einschließlich Paketregistern, GitHub, NVD, OSV.dev und OpenSSF Scorecard. Zuletzt aktualisiert: 2026-04-09. Maschinenlesbare Daten (JSON).

Ist Builder Vite sicher?

CAUTION — Builder Vite has a Nerq Trust Score of 62.8/100 (C). Es hat moderat Vertrauenssignale, zeigt aber einige Problembereiche that warrant attention. Suitable for development use — review Sicherheit and Wartung signals before production deployment.

Sicherheitsanalyse → Builder Vite Datenschutzbericht →

Was ist die Vertrauensbewertung von Builder Vite?

Builder Vite hat eine Nerq-Vertrauensbewertung von 62.8/100 und erhält die Note C. Diese Bewertung basiert auf 1 unabhängig gemessenen Dimensionen.

Konformität
100

Was sind die wichtigsten Sicherheitsergebnisse für Builder Vite?

Das stärkste Signal von Builder Vite ist konformität mit 100/100. Es wurden keine bekannten Schwachstellen erkannt. Hat die Nerq-Vertrauensschwelle von 70+ noch nicht erreicht.

Konformität: 100/100 — covers 52 of 52 jurisdictions

Was ist Builder Vite und wer pflegt es?

AutorGitHub Actions
KategorieUncategorized
Quellehttps://www.npmjs.com/package/@storybook/builder-vite

Regulatorische Konformität

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

Builder Vite auf anderen Plattformen

Gleicher Entwickler/Unternehmen in anderen Registern:

@nuxtjs/color-mode
76/100 · npm
@nomicfoundation/hardhat-zod-utils
74/100 · npm
@nomicfoundation/slang
72/100 · npm
@nomicfoundation/hardhat-viem-assertions
70/100 · npm
@nomicfoundation/hardhat-mocha
70/100 · npm

What Is Builder Vite?

Builder Vite is a software tool in the uncategorized category: A Storybook builder to dev and build with Vite. Nerq Trust Score: 63/100 (C).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including Sicherheit vulnerabilities, Wartung activity, license Konformität, and Community-Akzeptanz.

How Nerq Assesses Builder Vite's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five Dimensionen. Here is how Builder Vite performs in each:

The overall Trust Score of 62.8/100 (C) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Who Should Use Builder Vite?

Builder Vite is designed for:

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

How to Verify Builder Vite's Safety Yourself

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

  1. Check the source code — Überprüfen Sie das/die repository Sicherheit policy, open issues, and recent commits for signs of active Wartung.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Builder Vite's dependency tree.
  3. Bewertung permissions — Understand what access Builder Vite requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Builder Vite 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=@storybook/builder-vite
  6. Überprüfen Sie das/die license — Confirm that Builder Vite'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 Sicherheit concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Builder Vite

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

Data handling

Understand how Builder Vite processes, stores, and transmits your data. Überprüfen Sie das/die tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency Sicherheit

Check Builder Vite's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher Sicherheit risk.

Update frequency

Regularly check for updates to Builder Vite. Sicherheit patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Builder Vite 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 Konformität

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

Best Practices for Using Builder Vite Safely

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

Conduct regular audits

Periodically review how Builder Vite is used in your workflow. Check for unexpected behavior, permissions drift, and Konformität with your Sicherheit policies.

Keep dependencies updated

Ensure Builder Vite and all its dependencies are running the latest stable versions to benefit from Sicherheit patches.

Follow least privilege

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

Monitor for Sicherheit advisories

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

When Should You Avoid Builder Vite?

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

For each scenario, evaluate whether Builder Vite's trust score of 62.8/100 meets your organization's risk tolerance. We recommend running a manual Sicherheit assessment alongside the automated Nerq score.

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

This positions Builder Vite favorably among uncategorized tools. While it outperforms the average, there is still room for improvement in certain trust Dimensionen.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderat 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 Builder Vite 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 Wartung patterns change, Builder Vite'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 Sicherheit and quality. Conversely, a downward trend may signal reduced Wartung, growing technical debt, or unresolved vulnerabilities. To track Builder Vite's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=@storybook/builder-vite&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 — Sicherheit, Wartung, Dokumentation, Konformität, and community — has evolved independently, providing granular visibility into which aspects of Builder Vite are strengthening or weakening over time.

Wichtigste Punkte

Häufig gestellte Fragen

Ist Builder Vite sicher?
Mit Vorsicht verwenden. @storybook/builder-vite mit einem Nerq-Vertrauenswert von 62.8/100 (C). Stärkstes Signal: konformität (100/100). Bewertung basierend auf multiple trust Dimensionen.
Was ist die Vertrauensbewertung von Builder Vite?
@storybook/builder-vite: 62.8/100 (C). Bewertung basierend auf multiple trust Dimensionen. Compliance: 100/100. Bewertungen werden aktualisiert, wenn neue Daten verfügbar werden. API: GET nerq.ai/v1/preflight?target=@storybook/builder-vite
Was sind sicherere Alternativen zu Builder Vite?
In der Kategorie Uncategorized, weitere software tool werden analysiert — schauen Sie bald wieder vorbei. @storybook/builder-vite scores 62.8/100.
Wie oft wird die Sicherheitsbewertung von Builder Vite aktualisiert?
Nerq continuously monitors Builder Vite and updates its trust score as new data becomes available. Current: 62.8/100 (C), last verifiziert 2026-04-09. API: GET nerq.ai/v1/preflight?target=@storybook/builder-vite
Kann ich Builder Vite in einer regulierten Umgebung verwenden?
Builder Vite hat die Nerq-Verifizierungsschwelle von 70 nicht erreicht. Zusätzliche Prüfung empfohlen.
API: /v1/preflight Trust Badge API Docs

Siehe auch

Disclaimer: Nerq-Vertrauensbewertungen sind automatisierte Bewertungen basierend auf öffentlich verfügbaren Signalen. Sie sind keine Empfehlungen oder Garantien. Führen Sie immer Ihre eigene Sorgfaltsprüfung durch.

Wir verwenden Cookies für Analysen und Caching. Datenschutz