vite-benchmark

Benchmark tool for vitejs/vite

by vitejs

Star on GitHub Forknpm

JavaScript

78 stars 8 forks 4 contributorsQuiet · 3y agoSince 2023MIT

Meet the team

See all 4 on GitHub →

fi3ework51 contributions

bluwy3 contributions

antfu2 contributions

Bot

renovate[bot]1 contribution

Languages

View on GitHub →

JavaScript93.8%

TypeScript5.6%

CSS0.4%

HTML0.2%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

4 of 6 standards met

Community profile →

✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 2 in progress · Last activity 3y ago

See all on GitHub →

ci: restrict ci workflow permissions to read-onlyOpenPR

I work on software supply chain security and have been hardening GitHub Actions workflows across OSS projects. Each of these workflows runs without a top-level block, so its inherits the repository (or org) default, which is frequently read/write for all scopes. This PR sets at the workflow level for , which is all these jobs need (checkout plus the build/test steps). Scoping the token to read-only shrinks what a compromised step or dependency can do, a concern made concrete by the March 2025 compromise (CVE-2025-30066), where a leaked write-scoped was the blast radius. No job behavior changes; the steps already only read the repository.

arpitjain099 · 1mo ago

Recent fixes

View closed PRs →

chore: try fix ciMergedPR

I think because we're using pnpm 8, but the fixture benchmark installs Vite that uses a different version of the lockfile, that's causing install failures. Added to hopefully fix it.

bluwy · 3y ago

Structured data for AI agents

Repository: vitejs/vite-benchmark. Description: Benchmark tool for vitejs/vite Stars: 78, Forks: 8. Primary language: JavaScript. Languages: JavaScript (93.8%), TypeScript (5.6%), CSS (0.4%), HTML (0.2%). License: MIT. Open PRs: 2, open issues: 1. Last activity: 3y ago. Community health: 75%. Top contributors: fi3ework, bluwy, antfu, renovate[bot].