A program for reading smart-card documents issued by the government of Serbia
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 75%
Response Time: 1d
First Timer Success: 100%
ubavic/bas-celik has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ubavic/bas-celik respond to incoming external pull requests in approximately 24.9 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 53.1 places ubavic/bas-celik in the B tier.
The external contributor pull request merge rate for ubavic/bas-celik is 75.0%, based on public PR activity from non-core contributors.
ubavic/bas-celik currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in ubavic/bas-celik. Reviews community pull requests with focus on project quality.
Discussions in ubavic/bas-celik 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/ubavic/bas-celik?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (94% approval). Large PRs (>500 lines) take ~120 hours (34% approval). Keep your diff compact for rapid review.
Potrebno je implementirati učitavanje sertifikata sa saobraćajne dozvole i validaciju podataka. Pogledati Council Directive 1999/37/EC of 29 April 1999 on the registration documents for vehicles
Potrebno je implementirati učitavanje sertifikata sa zdravstvene knjižice i validaciju podataka
Trenutno, Baš Čelik preuzima samo podatak do kada osiguranje važi. Neophodno je proveriti da li zvanična aplikacija preuzima još neke podatke, i u potvrdnom odgovoru implementirati funkcionalnost u Baš Čeliku
Podaci koji se nalaze na saobraćajnoj dozvoli su standardizovani u čitavoj EU. Baš Čelik bi uz minimalne dorade mogao da pročita bilo koju odo ovih kartica. Neophodno je prvo utvrditi koje sve države koriste eVRC i koji su odgovarajući ATR nizovi.
Iako CROSO dozvoljava logovanje preko eUprave, potpisivanje dokumenata zahteva aplikaciju. Strategija za implementaciju je ista kao za #58
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 ubavic/bas-celik, 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 ubavic/bas-celik acknowledge new external contributions in approximately 1 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.
ubavic/bas-celik has a recorded first-timer success rate of 100.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 53.1 places ubavic/bas-celik in the Solid tier.
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.
Yes, ubavic/bas-celik currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ubavic/bas-celik 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.