Pine Script-compatible Python runtime for indicators and strategies, validated against TradingView on real published scripts
C-Rank Grade: B (Solid) - 42/100
External PR Merge Rate: 25%
Response Time: 1d
First Timer Success: -
PyneSys/pynecore has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PyneSys/pynecore respond to incoming external pull requests in approximately 34.5 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 41.9 places PyneSys/pynecore in the B tier.
The external contributor pull request merge rate for PyneSys/pynecore is 25.0%, based on public PR activity from non-core contributors.
PyneSys/pynecore currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Python project in PyneSys/pynecore welcoming community pull requests and bug fixes.
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/PyneSys/pynecore?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~22 hours (31% approval). Large PRs (>500 lines) take ~166 hours (15% approval). Keep your diff compact for rapid review.
Summary For futures strategies, PyneCore users currently have to choose between: Raw per-contract Databento data, which jumps at roll boundaries and is not what TV charts show. Databento's pre-stitched .c.0 continuous feed, which uses a documented ratio/difference adjustment that does not match TradingView's proprietary continuous-contract algorithm (offset ~700 points on NQ vs CME_MINI:NQ1!). Either choice produces a price level mismatch vs TV. For ratio-based indicators that combine close with a moving average of close — BBW = 2*stdev(close,9)/sma(close,9), PMAR = close/vwma(close,20) — the ~700pt offset between TV's continuous and Databento's specific contract cascades into ~3pct BBW divergence and 7-10 absolute points of BBWP / PMARP percentile drift. That in turn produces ~19-24pct trade-level filter disagreement when running the same Pine source on TV vs PyneCore. We solved this on our side with the reconstruction algorithm below (Apache-2.0, ~300 lines of Python over raw D
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 PyneSys/pynecore, 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 PyneSys/pynecore acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.0% were successfully merged into the primary branch.
PyneSys/pynecore has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 41.9 places PyneSys/pynecore in the Solid tier.
The external pull request merge rate is 25.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PyneSys/pynecore currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PyneSys/pynecore 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.