nexu-io/html-video - Open Source PR Review Scorecard

Programmatic video for coding agents — HTML to video on your laptop. Turn HTML, CSS & data into real MP4s with pluggable render engines, 21 templates, AI soundtrack. Apache-2.0, no per-render fees. An official project by the Open Design team.

C-Rank Grade: B (Solid) - 49/100

External PR Merge Rate: 42%

Response Time: <1h

First Timer Success: 50%

Frequently Asked Questions

Is nexu-io/html-video welcoming to first-time open-source contributors?

nexu-io/html-video has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in nexu-io/html-video respond to incoming external pull requests in approximately 0.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 48.5 C-Rank™ score (B Tier) represent?

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 48.5 places nexu-io/html-video in the B tier.

What is the external contributor pull request merge rate for nexu-io/html-video?

The external contributor pull request merge rate for nexu-io/html-video is 42.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in nexu-io/html-video?

nexu-io/html-video currently has 14 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

nexu-io
nexu-io/html-videoB•Solid4.7k
GitHub
Back to Explorer
nexu-io

nexu-io/html-video

4,660
InactiveB•Solid(49/100)Low Sample (<20 PRs)HTML

Programmatic video for coding agents — HTML to video on your laptop. Turn HTML, CSS & data into real MP4s with pluggable render engines, 21 templates, AI soundtrack. Apache-2.0, no per-render fees. An official project by the Open Design team.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in nexu-io/html-video. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in nexu-io/html-video focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
42.1%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
42.1%
Merge Gauge
50.0%
1st-Timer
Community Vibe62/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for nexu-io/html-video
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/nexu-io/html-video)](https://getmerged.abhishekco.de/nexu-io/html-video?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

While reading the codebase I noticed the notes already discuss calling hyperframes render via child_process.spawn as the intended render path, but it hasn't been implemented yet. Raising this as a feature request. Benefits HTML generation via HF skills — hyperframes-animation / hyperframes-creative encode the full authoring contract (data-* attributes, single paused timeline, seek-safe constraints) and 24+ validated animation recipes. Using them directly produces output that passes hyperframes lint by construction, which a hand-rolled prompt cannot guarantee. No need to reimplement or maintain the render pipeline — the current adapter reimplements font loading, GSAP pause/seek/resume, multi-composition inlining, duration probing, and ffmpeg transcoding. Calling hyperframes render returns all of that to upstream. Is this on the roadmap? Would a PR be welcome?

📅 Opened Jul 9, 2026💬 4 comments
Quality: 40/100Contribute

Summary The current BYOK mode only supports the Anthropic Messages API (anthropic-api). I'd like to add an openai-api HTTP agent that speaks the OpenAI Chat Completions protocol (POST /v1/chat/completions), using the same kind: 'http' extension point already established by anthropic-api. This single addition covers a large surface of providers without any further changes, since most modern LLM APIs implement the OpenAI-compatible interface: OpenAI, Azure OpenAI, Groq, Together AI, Fireworks, Ollama, LM Studio, and any other OpenAI-shim provider. Motivation Many users already have an OpenAI API key and no Anthropic key. Self-hosted / local inference stacks (Ollama, LM Studio, vLLM) expose /v1/chat/completions — this would make html-video usable fully offline without a CLI agent installed. The runtime already has a clean AgentDef.httpHandler + httpProbe interface (packages/runtime/src/types.ts), so this is a contained addition with no interface changes. I'm happy to submit a PR for t

📅 Opened Jun 29, 2026💬 6 comments
Quality: 40/100Contribute

On Windows, the background music preview in Studio uses the native element. I noticed several playback issues: Total duration is not shown immediately after the audio loads. The progress bar jumps backward after pausing. The progress bar reaches the end before the music actually finishes. These make it hard to preview the soundtrack accurately.I’m willing to submit a PR to fix this by replacing the native player with a custom playback component, so we can manage currentTime, duration, and play state consistently across browsers. Environment OS: Windows 11 22H2

📅 Opened Jun 25, 2026💬 27 comments
Quality: 40/100Contribute

Running on Windows, I hit two issues with the Soundtrack feature: Audio preview fails to load (HTTP 403) — The /asset endpoint's path validation only matches forward slashes, but path.resolve() returns backslash paths on Windows, so the check always fails. Both AI-generated and manually registered audio assets can't play. Audio preview placement is hard to notice — The preview player sits at the very bottom of the Soundtrack panel, far from the "Generate music" button. It should appear directly below each generate button instead. I have fixes ready for both and would be happy to submit a PR.

📅 Opened Jun 25, 2026💬 9 comments
Quality: 40/100Contribute

Code Audit Report All findings are reviewed for confidence before posting. Please verify each finding before acting on it. Repository: nexu-io/html-video Findings: 26 issue(s) found — 🟠 6 high · 🟡 9 medium · 🔵 11 low 1. 🔒 SSRF protection bypass via IPv6 addresses Field Details Severity 🟠 High Type Security File packages/cli/src/fetch-source.ts Location assertPublicHttpUrl Confidence 92% Problem: The assertPublicHttpUrl function validates that a URL is public by checking the hostname against a list of disallowed hostnames and IPv4 private ranges. However, it does not inspect IPv6 addresses (e.g., "[::1]", "[fe80::1]") or IPv4‑mapped IPv6 addresses (e.g., "::ffff:127.0.0.1"). An attacker could supply a malicious IPv6 address that resolves to a private or loopback interface, bypassing the SSRF guard and allowing the server to fetch internal resources. Suggested Fix: Extend the validation to parse and reject IPv6 addresses that fall within loopback

📅 Opened Jun 16, 2026💬 5 comments
Quality: 25/100Contribute
Looking for more HTML beginner tasks?Explore HTML GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for nexu-io/html-video

When evaluating whether to contribute to nexu-io/html-video, 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 nexu-io/html-video acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 42.1% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to nexu-io/html-video

01

Is nexu-io/html-video welcoming to first-time open-source contributors?

nexu-io/html-video has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 48.5 C-Rank™ score represent?

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 48.5 places nexu-io/html-video in the Solid tier.

04

What is the external contributor pull request merge rate for nexu-io/html-video?

The external pull request merge rate is 42.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in nexu-io/html-video?

Yes, nexu-io/html-video currently has 14 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for nexu-io/html-video 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.