A free and open-source java bytecode obfuscator with advanced features
C-Rank Grade: B (Solid) - 43/100
External PR Merge Rate: 67%
Response Time: 2d
First Timer Success: 67%
LvStrnggg/aidsfuscator has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LvStrnggg/aidsfuscator respond to incoming external pull requests in approximately 58.3 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 43.0 places LvStrnggg/aidsfuscator in the B tier.
The external contributor pull request merge rate for LvStrnggg/aidsfuscator is 66.7%, based on public PR activity from non-core contributors.
LvStrnggg/aidsfuscator currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in LvStrnggg/aidsfuscator. Maintains strict focus on technical quality and test standards.
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/LvStrnggg/aidsfuscator?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~38 hours (83% approval). Large PRs (>500 lines) take ~280 hours (30% approval). Keep your diff compact for rapid review.
There is a bug currently with the method (and potentially even field) renamer which, at a bit more complex (not really) hierarchies breaks VIA name collision (more prominent with aggressive overloading set to true). This was tested on a ~3mb snake game jar (attached below alongside all of the libraries). The collisions happen in 2 or 3 classes. One of them is org.apache.logging.log4j.util.SortedArrayStringMap, which has name collisions with methods isEmpty()Z and isFrozen()Z. I have tried multiple solutions to try and tackle this issue, but to no avail. I even wrote code which detected name collisions before renaming, yet it still decided to collide names. isEmpty and isFrozen both get remapped to a. Combine that with matching descriptors and you get a ClassFormatError thrown. I personally think the issue lies in the hierarchy/how methods get mapped/win names from methods who already have these methods mapped. In the latest commit, I have added a DuplicateMethodCheckTransformer in the
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 LvStrnggg/aidsfuscator, 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 LvStrnggg/aidsfuscator acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
LvStrnggg/aidsfuscator has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 43.0 places LvStrnggg/aidsfuscator in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, LvStrnggg/aidsfuscator 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 LvStrnggg/aidsfuscator 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.