@nuxt/vite-builder-nightly

MITLicense declared in the package manifest.

Vite bundler for Nuxt

91

Security score

0 known advisories in v4.6.0-29853280.6c7f9fd4

OpenSSF Scorecard 7.0/10

0-100 score computed by this site from verifiable signals only: known OSV.dev advisories affecting this exact version, how recently it was published, and the repository's OpenSSF Scorecard.advisory penalty −0 · staleness penalty −0 · scorecard component 70/100 (30% weight)

Weekly downloads

Downloads across all versions in the last 7 days, from the official npm downloads API (api.npmjs.org).

—

Unpacked size

Size of v4.6.0-29853280.6c7f9fd4 on disk after npm install extracts the tarball, as reported by the npm registry.

167.4 kB

Dependencies

Direct runtime dependencies declared by v4.6.0-29853280.6c7f9fd4. Transitive dependencies are not counted here — use the lockfile audit for the full tree.

28

Last publish

When v4.6.0-29853280.6c7f9fd4 was published to the registry. Long gaps can indicate an unmaintained package.

6 hours ago

Security advisories

Vulnerabilities affecting v4.6.0-29853280.6c7f9fd4 specifically, from OSV.dev — the open database aggregating the GitHub Advisory Database (GHSA) and CVEs. Links open the full advisory.

No known vulnerabilities affect v4.6.0-29853280.6c7f9fd4.

OpenSSF ScorecardAug 24, 2026

OpenSSF Scorecard is an automated audit of the source repository's security practices, run by the Open Source Security Foundation. Each check scores 0-10; hover a check for what it means. Data via deps.dev.
  • MaintainedThe project shows recent activity: commits or issue triage within the last 90 days.Result: 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 1010
  • Code-ReviewChanges are reviewed by another maintainer before landing on the main branch.Result: Found 6/25 approved changesets -- score normalized to 22
  • Security-PolicyA SECURITY.md explains how to report vulnerabilities privately.Result: security policy file detected10
  • Dangerous-WorkflowGitHub Actions workflows avoid dangerous patterns such as untrusted code checkout or script injection.Result: no dangerous workflow patterns detected10
  • CII-Best-PracticesThe project holds an OpenSSF Best Practices badge, a self-certification of security practices.Result: badge detected: InProgress2
  • Token-PermissionsCI workflow tokens follow least privilege — read-only unless a job needs more.Result: GitHub workflow tokens follow principle of least privilege10
  • Binary-ArtifactsNo compiled binaries are committed to the repository — binaries can't be reviewed and may hide malicious code.Result: binaries present in source code9
  • LicenseThe project publishes a license file.Result: license file detected10
  • Pinned-DependenciesBuild dependencies are pinned to exact versions or hashes, preventing silent supply-chain swaps.Result: dependency not pinned by hash detected -- score normalized to 99
  • Branch-ProtectionThe default branch is protected: force pushes are blocked and changes require review before merging.Result: branch protection not enabled on development/release branches0
  • FuzzingThe project is fuzz-tested (e.g. OSS-Fuzz), which finds crashes and memory bugs automatically.Result: project is not fuzzed0
  • SASTStatic analysis (e.g. CodeQL) runs on pull requests to catch bugs before merge.Result: SAST tool is run on all commits10