Detect license usage restrictions in your project!
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 88%
Response Time: 2d
First Timer Success: 100%
anistark/feluda 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 anistark/feluda respond to incoming external pull requests in approximately 47.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.8 places anistark/feluda in the B tier.
The external contributor pull request merge rate for anistark/feluda is 87.5%, based on public PR activity from non-core contributors.
anistark/feluda currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in anistark/feluda. Reviews community pull requests with focus on project quality.
Discussions in anistark/feluda 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/anistark/feluda?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~31 hours (96% approval). Large PRs (>500 lines) take ~230 hours (39% approval). Keep your diff compact for rapid review.
Summary A standard BSD-2-Clause or BSD-3-Clause license file never has to contain the word "BSD", and the canonical texts (the ones opensource.org publishes and Pallets, for example, ships verbatim) do not. Feluda's content rules require a literal BSD marker, so those files are not recognised in any scan mode. Seen on a --filesystem scan of python:3.12-slim with pip install flask: Jinja2 and itsdangerous report unknown although both ship the full BSD-3-Clause text in their dist-info. Current state The two BSD rules in LICENSE_CONTENT_RULES each require BSD alongside Redistribution and use: https://github.com/anistark/feluda/blob/fdc9562/src/licenses.rs#L1240-L1248 detect_license_from_content walks those rules for every scan mode: vendored and unmanaged directories, Debian copyright files, node_modules, the installed artifact probe and the manifest analyzers' license file fallback: https://github.com/anistark/feluda/blob/fdc9562/src/licenses.rs#L1363 Python classifiers do not help here
Summary A --filesystem scan of debian:12-slim reports 7 of 88 packages as unknown (base-files, libcrypt1, libselinux1, libtasn1-6 and three others). Their copyright files predate DEP-5 and state the license only in prose that points at /usr/share/common-licenses/<name>. Most of them name exactly one license, and a deliberately conservative rule could resolve those without guessing on the rest. Current state license_from_copyright tries DEP-5 first, then the generic content matcher: https://github.com/anistark/feluda/blob/fdc9562/src/filesystem/copyright.rs#L22 DEP-5 short names are mapped onto SPDX by normalize_debian_license: https://github.com/anistark/feluda/blob/fdc9562/src/filesystem/copyright.rs#L73 A pre-DEP-5 file such as "This package is licensed under the GNU GPL, see /usr/share/common-licenses/GPL-2" matches neither, so the package reports as unknown. That is by design: the cataloger never infers a license the file does not state (see the plan notes in the #252 implementati
Is your feature request related to a problem? Please describe. Feluda's Java/Gradle backend (added in #217) scans pom.xml, build.gradle, and build.gradle.kts and resolves transitive deps from Maven Central. Plain Kotlin-on-JVM libraries already work, because they use ordinary Maven Central coordinates. However, a real Android app — or a modern Kotlin-Gradle project — is significantly under-reported today, because three idioms that are now the default in Android Studio / current Gradle aren't handled: Version catalogs aren't parsed. Dependencies declared as implementation(libs.androidx.core.ktx) (resolved from gradle/libs.versions.toml) are missed entirely — the parser expects a literal "group:artifact:version" string, not a libs.* accessor. Google's Maven repository isn't queried. License + transitive lookup only hits repo1.maven.org (Maven Central). AndroidX and com.google.android.* artifacts live on maven.google.com, so they resolve to Unknown and don't expand transitively. pl
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 anistark/feluda, 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 anistark/feluda acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.5% were successfully merged into the primary branch.
anistark/feluda 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.8 places anistark/feluda in the Solid tier.
The external pull request merge rate is 87.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, anistark/feluda currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for anistark/feluda 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.