Er Builder Vite sikker?

Builder Vite — Nerq Trust Score 62.8/100 (Karakter C). Baseret på analyse af 1 tillidsdimensioner vurderes det som generelt sikkert men med visse bekymringer. Sidst opdateret: 2026-04-09.

Brug Builder Vite med forsigtighed. Builder Vite er en software tool med en Nerq Tillidsscore på 62.8/100 (C), based on 3 uafhængige datadimensioner. Under Nerqs verificerede tærskel Data hentet fra flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sidst opdateret: 2026-04-09. Maskinlæsbare data (JSON).

Er Builder Vite sikker?

CAUTION — Builder Vite has a Nerq Trust Score of 62.8/100 (C). Har moderat tillidssignaler, men viser nogle bekymrende områder that warrant attention. Suitable for development use — review sikkerhed and vedligeholdelse signals before production deployment.

Sikkerhedsanalyse → Builder Vite privatlivsrapport →

Hvad er Builder Vites tillidsscore?

Builder Vite har en Nerq Trust Score på 62.8/100 med karakteren C. Denne score er baseret på 1 uafhængigt målte dimensioner, herunder sikkerhed, vedligeholdelse og community-adoption.

Overholdelse
100

Hvad er de vigtigste sikkerhedsresultater for Builder Vite?

Builder Vites stærkeste signal er overholdelse på 100/100. Ingen kendte sårbarheder er fundet. It has not yet reached the Nerq Verified threshold of 70+.

Overholdelse: 100/100 — covers 52 of 52 jurisdictions

Hvad er Builder Vite og hvem vedligeholder det?

UdviklerGitHub Actions
KategoriUncategorized
Kildehttps://www.npmjs.com/package/@storybook/builder-vite

Lovgivningsmæssig overholdelse

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

Builder Vite på andre platforme

Samme udvikler/virksomhed i andre registre:

@nuxtjs/color-mode
76/100 · npm
@nomicfoundation/hardhat-zod-utils
74/100 · npm
@nomicfoundation/slang
72/100 · npm
@nomicfoundation/hardhat-mocha
70/100 · npm
@nomicfoundation/hardhat-viem-assertions
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 sikkerhed vulnerabilities, vedligeholdelse activity, license overholdelse, and fællesskabsadoption.

How Nerq Assesses Builder Vite's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensioner. 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 sikkerhed 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 — Gennemgå repository sikkerhed policy, open issues, and recent commits for signs of active vedligeholdelse.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Builder Vite's dependency tree.
  3. Anmeldelse 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. Gennemgå 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 sikkerhed 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. Gennemgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sikkerhed

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

Update frequency

Regularly check for updates to Builder Vite. Sikkerhed 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 overholdelse

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 overholdelse with your sikkerhed policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for sikkerhed advisories

Subscribe to Builder Vite's sikkerhed 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 sikkerhed 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 dimensioner.

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 vedligeholdelse 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 sikkerhed and quality. Conversely, a downward trend may signal reduced vedligeholdelse, 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 — sikkerhed, vedligeholdelse, dokumentation, overholdelse, and community — has evolved independently, providing granular visibility into which aspects of Builder Vite are strengthening or weakening over time.

Vigtigste pointer

Ofte stillede spørgsmål

Er Builder Vite sikker?
Brug med forsigtighed. @storybook/builder-vite med en Nerq Tillidsscore på 62.8/100 (C). Stærkeste signal: overholdelse (100/100). Score baseret på multiple trust dimensioner.
Hvad er Builder Vites tillidsscore?
@storybook/builder-vite: 62.8/100 (C). Score baseret på multiple trust dimensioner. Compliance: 100/100. Scorer opdateres når nye data bliver tilgængelige. API: GET nerq.ai/v1/preflight?target=@storybook/builder-vite
Hvad er sikrere alternativer til Builder Vite?
I kategorien Uncategorized, flere software tool analyseres — kom snart tilbage. @storybook/builder-vite scores 62.8/100.
Hvor ofte opdateres Builder Vites sikkerhedsscore?
Nerq continuously monitors Builder Vite and updates its trust score as new data becomes available. Current: 62.8/100 (C), last verificeret 2026-04-09. API: GET nerq.ai/v1/preflight?target=@storybook/builder-vite
Kan jeg bruge Builder Vite i et reguleret miljø?
Builder Vite har ikke nået Nerq-verificeringstærsklen på 70. Yderligere gennemgang anbefales.
API: /v1/preflight Trust Badge API Docs

Se også

Disclaimer: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.

Vi bruger cookies til analyse og caching. Privatliv