Vite+ is the unified toolchain and entry point for web development. It manages your runtime, package manager, and frontend toolchain in one place.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 79%
Response Time: 3d
First Timer Success: 75%
voidzero-dev/vite-plus has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in voidzero-dev/vite-plus respond to incoming external pull requests in approximately 61.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 59.3 places voidzero-dev/vite-plus in the A tier.
The external contributor pull request merge rate for voidzero-dev/vite-plus is 78.8%, based on public PR activity from non-core contributors.
voidzero-dev/vite-plus currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in voidzero-dev/vite-plus. Ensure PR scope matches issue requirements closely before requesting review.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/voidzero-dev/vite-plus?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~40 hours (96% approval). Large PRs (>500 lines) take ~293 hours (35% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Rust.
Confidential Containers Guest Tools and Components
This is a solidity implementation of IBC v2.
Rust tool to detect cell site simulators on an orbic mobile hotspot
Summary Direct user feedback suggests vp up -i would be more useful if it linked to changelog information rather than the generic package URL. Reference: https://bsky.app/profile/nestor.rip/post/3mssje4iqu22g Requested change For vp up -i, show an npmx link to the package changelog instead of the package URL Why this matters When reviewing updates interactively, changelog context is often more actionable than a homepage or package URL.
Description Currently vp run doesn't seem to have a way to suppress the script command line and other vp diagnostic info, e.g. $ vp run --cache check ~/cmd/admin-web$ vp check ◉ cache hit, replaying pass: All 162 files are correctly formatted (331ms, 14 threads) pass: Found no warnings, lint errors, or type errors in 77 files (1.4s, 14 threads) --- vp run: cache hit, 1.96s saved. The command line and diagnostics info is sometimes pure noise and in agentic settings only waste tokens when shown repeatedly in verification gates. Other major JS toolchains all have --silent option in their run command, but AFAICT vp run only has --verbose adding more output, not less. Suggested solution Simply add a -s, --silent option like other toolchains (npm/pnpm/yarn/bun/etc.): $ vp run --silent --cache check pass: All 162 files are correctly formatted (331ms, 14 threads) pass: Found no warnings, lint errors, or type errors in 77 files (1.4s, 14 threads) Alternative No response Additional context No
Description Coming from https://discord.com/channels/1079625926024900739/1429522693190979685/1482723054143672341 We already created a VSCode extension which include oxc.oxc-vscode and vitest.explorer VSCode extension. https://github.com/voidzero-dev/vite-plus-extension-pack The same extension pack is missing for IntelliJ/JetBrains Editors. Suggested solution Asked ChatGPT if there is a concept like VS Code extensionPack for IntelliJ. 1. Create a normal IntelliJ plugin You can create it using the IntelliJ Platform Gradle Plugin or the plugin template. Typical structure: my-meta-plugin/ ├─ build.gradle.kts ├─ settings.gradle.kts └─ src/main/resources/META-INF/plugin.xml 2. Declare plugin dependencies in plugin.xml Add the plugins you want to bundle as required dependencies: <idea-plugin> <id>com.example.my-plugin-pack</id> <name>My Plugin Pack</name> <vendor email="[email protected]">Me</vendor> <!-- Dependencies --> <depends>org.intellij.plugins.markdow
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to voidzero-dev/vite-plus, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of voidzero-dev/vite-plus acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.8% were successfully merged into the primary branch.
voidzero-dev/vite-plus has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 59.3 places voidzero-dev/vite-plus in the Welcoming tier.
The external pull request merge rate is 78.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, voidzero-dev/vite-plus currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for voidzero-dev/vite-plus are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.