silexlabs/Silex - Open Source PR Review Scorecard

Silex is an online tool for visually creating static sites with dynamic data. With the free/libre spirit of internet, together.

C-Rank Grade: S (Elite) - 71/100

External PR Merge Rate: 75%

Response Time: 2d

First Timer Success: 33%

Frequently Asked Questions

Is silexlabs/Silex welcoming to first-time open-source contributors?

silexlabs/Silex has a recorded first-timer success rate of 33.3%. Repositories ranked S 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 silexlabs/Silex respond to incoming external pull requests in approximately 53.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 70.7 C-Rank™ score (S 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 70.7 places silexlabs/Silex in the S tier.

What is the external contributor pull request merge rate for silexlabs/Silex?

The external contributor pull request merge rate for silexlabs/Silex is 75.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in silexlabs/Silex?

silexlabs/Silex currently has 18 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

silexlabs
silexlabs/SilexS•Elite3.0k
GitHub
Back to Explorer
silexlabs

silexlabs/Silex

2,997
Active (30d)S•Elite(71/100)TypeScript

Silex is an online tool for visually creating static sites with dynamic data. With the free/libre spirit of internet, together.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

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

Active TypeScript repository in silexlabs/Silex with ongoing community development and issue triage.

Top PR Submission Do's

  • •Ensure code complies with TypeScript style conventions
  • •Keep PRs scoped and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
75.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
33.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
10 core
Highly collaborative maintainer core
Diagnostic Health HUD
75.0%
Merge Gauge
33.3%
1st-Timer
Community Vibe40/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

The slice filter gives a different result in the editor and on the published site when the first number is not 0. In the editor preview, the second number is an end index. On the published site, the second number is a length (the number of items to keep). How to reproduce: Make an element repeat over a list from a data source, for example a list of 5 posts or more. Add the slice filter to this list. Type 2 in "Start index" and 3 in "End index". Look at the editor preview: it shows 1 post (the 3rd one). Publish the site and open it: it shows 3 posts (the 3rd, 4th and 5th). With 0 and 3, the editor and the published site both show 3 posts. The problem appears only when the first number is not 0. Why this happens: In the editor, the filter uses JavaScript Array.slice(start, end). The second number is the index where the list stops. On the published site, the filter becomes the Liquid filter slice: start, length. The second number is how many items to keep. Code: grapesjs-plugins/grapes

📅 Opened Oct 6, 2026💬 0 comments
Quality: 90/100Contribute

When several elements are selected, the selector area shows "Select a component to edit its selector". You cannot add a class to all of them at once. At the same time, the Style Manager still works. It styles the classes the elements share. With several Containers selected, this is .silex-default-container, so the change goes to every Container of the website. There is no warning. Steps to reproduce Add three Containers to a page. Do not give them any class. Select the first one, then Shift+click the two others. Look at the selector area: it shows "Select a component to edit its selector". In the Style Manager, change the background color. All Containers of the website change, not only the three selected ones. If the three Containers share a class card, the style goes to .silex-default-container.card. Where to look The code is in grapesjs-plugins/grapesjs-advanced-selector/src/. model/ComplexSelector.ts, function getSelector: it calls same() on the selectors of the selected componen

📅 Opened Oct 6, 2026💬 2 comments
Quality: 90/100Contribute

The Display select in the Style Manager offers grid, but Silex has no grid properties (no grid-template-columns, grid-column…). With only display: grid, the element shows one column, which is confusing. The option is in editor/grapesjs/css-props.ts, in the display property. Please remove it, then check in Silex that the Display select still works.

📅 Opened Oct 6, 2026💬 3 comments
Quality: 90/100Contribute

The Display option has inherit, initial and unset, but not revert. Please add it. We need it for menus made with the popover attribute: on mobile, display: revert lets the browser hide the menu when it is closed and show it when it is open. unset and initial do not do that. This comes from "Missing focus management on burger menu overlay" (#1665) Please test it yourself in a browser and add a screenshot in your pull request :)

📅 Opened Sep 30, 2026💬 1 comment
Quality: 90/100Contribute

Problem Today there is no clear way to publish an image with an empty alt="". In the Attributes panel, if you add alt with an empty value, the attribute is removed from the HTML. In the Settings (traits), an empty alt field gives no alt at all. If you type text and then erase it, you do not get alt="", it just removes the attribute too Decorative images need alt="", so screen readers skip them. But empty alt must not become the default: then every image would be "decorative" and nobody would write real alt text. Proposal Add a "Decorative image" checkbox next to the alt field in the image traits: checked: the alt field is disabled and the image is published with alt="" not checked: the alt field works as today This is what Webflow does ("Decorative" option in the Alt text menu). This isssue is releated to "The nudge for missing alt text" (#1736)

📅 Opened Sep 28, 2026💬 1 comment
Quality: 90/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 silexlabs/Silex

When evaluating whether to contribute to silexlabs/Silex, 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 silexlabs/Silex acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to silexlabs/Silex

01

Is silexlabs/Silex welcoming to first-time open-source contributors?

silexlabs/Silex has a recorded first-timer success rate of 33.3%. Repositories ranked Elite 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 ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 70.7 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 70.7 places silexlabs/Silex in the Elite tier.

04

What is the external contributor pull request merge rate for silexlabs/Silex?

The external pull request merge rate is 75.0%. 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 silexlabs/Silex?

Yes, silexlabs/Silex currently has 18 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 silexlabs/Silex 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.