High-performance technical analysis indicators and backtesting framework in Go. Zero dependencies. ✨ See how! 👀
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 70%
Response Time: <1h
First Timer Success: 100%
cinar/indicator has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cinar/indicator respond to incoming external pull requests in approximately 0.0 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 64.4 places cinar/indicator in the A tier.
The external contributor pull request merge rate for cinar/indicator is 70.0%, based on public PR activity from non-core contributors.
cinar/indicator currently has 15 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in cinar/indicator. Reviews community pull requests with focus on project quality.
Discussions in cinar/indicator focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/cinar/indicator?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (88% approval). Large PRs (>500 lines) take ~0 hours (32% approval). Keep your diff compact for rapid review.
Description Returns 1 if the current value is strictly greater than the historical value, and 0 otherwise. Math/Formula $$\text{IsRising}_t = \begin{cases} 1 & \text{if } P_t > P_{t-n} \ 0 & \text{otherwise} \end{cases}$$ Implementation Details Generic helper function under the helper package. Signature: func IsRising[T Number](c <-chan T, period int) <-chan T Parameters: period (default: 1) Test files with 100% coverage. Suggested Package helper
Description Normalizes True Range against the closing price to measure trend volatility quality. Math/Formula $$\text{VQ} = \text{SMA}\left(\frac{\text{TrueRange}}{Close}, n\right)$$ Implementation Details Struct name: VolatilityQuotient[T helper.Number] Constructor: NewVolatilityQuotient[T helper.Number](), NewVolatilityQuotientWithPeriod[T helper.Number](period int) Parameters: period (default: 20) Functions: Compute(highs, lows, closings <-chan T) <-chan T, IdlePeriod() int, String() string Use the TrueRange implementation once added. Test files with 100% coverage. Suggested Package volatility
Implement the Know Sure Thing (KST) trading strategy using the existing trend.Kst indicator. Location: strategy/trend/kst_strategy.go Strategy Rules: Buy Action: KST crosses above its signal line (typically a 9-period SMA of KST). Sell Action: KST crosses below its signal line. Hold Action: Otherwise. Implementation Details: Follow the strategy.Strategy interface. Use trend.NewKst() and calculate a signal line using SMA. Provide unit tests with historical data in strategy/trend/testdata/kst_strategy.csv. Ensure 100% test coverage.
Implement the Fisher Transform trading strategy using the existing momentum.Fisher indicator. Location: strategy/momentum/fisher_strategy.go Strategy Rules: Buy Action: Fisher Transform value crosses above its signal line (which is a 1-period lagged Fisher value). Sell Action: Fisher Transform value crosses below its signal line. Hold Action: Otherwise. Implementation Details: Follow the strategy.Strategy interface. Use momentum.NewFisher() or allow custom parameters. Provide unit tests with historical data in strategy/momentum/testdata/fisher_strategy.csv. Ensure 100% test coverage.
Implement the Relative Vigor Index (RVI) trading strategy using the existing momentum.Rvi indicator. Location: strategy/momentum/rvi_strategy.go Strategy Rules: Buy Action: RVI crosses above its signal line. Sell Action: RVI crosses below its signal line. Hold Action: Otherwise. Implementation Details: Follow the strategy.Strategy interface. Use momentum.NewRvi() or allow custom parameters. Provide unit tests with historical data in strategy/momentum/testdata/rvi_strategy.csv. Ensure 100% test coverage.
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 cinar/indicator, 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 cinar/indicator acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
cinar/indicator has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 64.4 places cinar/indicator in the Welcoming tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cinar/indicator currently has 15 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for cinar/indicator 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.