MuntashirAkon/AppManager - Open Source PR Review Scorecard

A full-featured package manager and viewer for Android

C-Rank Grade: D (Risky) - 8/100

External PR Merge Rate: -

Response Time: -

First Timer Success: -

Frequently Asked Questions

Is MuntashirAkon/AppManager welcoming to first-time open-source contributors?

MuntashirAkon/AppManager has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in MuntashirAkon/AppManager 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.

What does the 7.5 C-Rank™ score (D Tier) represent?

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 7.5 places MuntashirAkon/AppManager in the D tier.

What is the external contributor pull request merge rate for MuntashirAkon/AppManager?

The external contributor pull request merge rate for MuntashirAkon/AppManager is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in MuntashirAkon/AppManager?

MuntashirAkon/AppManager currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

MuntashirAkon
MuntashirAkon/AppManagerD•Risky9.2k
GitHub
Back to Explorer
MuntashirAkon

MuntashirAkon/AppManager

9,208
InactiveD•Risky(8/100)Low Sample (<20 PRs)Java

A full-featured package manager and viewer for Android

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in MuntashirAkon/AppManager welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for MuntashirAkon/AppManager
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/MuntashirAkon/AppManager)](https://getmerged.abhishekco.de/MuntashirAkon/AppManager?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Please check before submitting an issue I have searched the issues and haven't found anything relevant I have read the docs I know that generating a report, in whole part or in part, using AI/LLM is prohibited Describe the existing feature/documentation I would like to understand the meaning of the enable/disable switches in the Activity list and how App Manager determines whether an Activity is enabled or disabled. Describe your problem(s) When viewing the Activities of an app, the switches appear to be enabled for all Activities, including those that have been disabled using another app (e.g. Blocker) through package manager (pm). I have also refreshed the list many times. I checked the output of adb shell dumpsys package <package_name> and found the relevant Activities listed under disabledComponents. I am not sure whether the switches represent the actual enabled state of each component, a state managed by App Manager itself, or something else. Could someone clarify the follow

📅 Opened Oct 10, 2026💬 0 comments
Quality: 75/100Contribute

I have searched the issues and haven't found anything relevant I have read the docs I know that generating a report, in whole part or in part, using AI/LLM is prohibited Hello ! I need to PERMANENTLY intercept action=android.intent.action.OPEN_DOCUMENT and replace it with action=android.intent.action.GET_CONTENT If you seen these two activities before, you are not crazy: they are both handled by Android's default Files app (package=com.android.documentsui), but with different result (the GET_CONTENT version has many more features) I successfully launched the modified activity, but it is not permanent. I need to make it permanent. Problem is: The android.intent.action.OPEN_DOCUMENT gives us no opportunity to Open As and select App Manager's Interceptor. It is always set to Files app, and has no way to clear Is there another way ?

📅 Opened Sep 5, 2026💬 0 comments
Quality: 75/100Contribute

Please check before submitting an issue I have searched the issues and haven't found anything relevant I have read the docs I know that generating a report, in whole part or in part, using AI/LLM is prohibited Describe the existing feature/documentation So First let me say english is not my mais english is my 4,so have patinete. My Google Playstore is 50gb ALL due tô the apps i installed over years,thete appear in App manager, uninstalled apps, and I can't remove them from there.Because there are so many and my app crashes, but searching by filtering for uninstalled apps in the app manager, I didn't see anything. So, any help please? Describe your problem(s) No response Additional context No response

📅 Opened May 8, 2026💬 1 comment
Quality: 55/100Contribute

Please check before submitting an issue I have searched the issues and haven't found anything relevant I have read the docs I know that generating a report, in whole part or in part, using AI/LLM is prohibited Describe the existing feature/documentation When searching I did find a slightly relevant issue #940 But for clarity I think separate one is better than posting in the old one Describe your problem(s) I suspect an app I have, well, "managed" rather bravely via AppManager is now misbehaving due to my tweaks (but it's an old, moody, janky app so chances are it's just naturally bad) I would like to revert changes to this app particularly. I did not make backups (of course :) ) So, question : Assuming no backups done, and assuming the app does not hold critical user data I would be afraid to lose Would uninstalling the app in question, rebooting, then re-installing it again revert changes done to that app by app manager ? Should I also compliment that uninstall-reboot-reinstall

📅 Opened Apr 26, 2026💬 1 comment
Quality: 70/100Contribute

Describe the existing feature/documentation Appop's permission changer Describe your problem(s) Android 16 NothingOS 4.0 Asteroids-B4.0-251229-2335 Hello, whenever I am trying to set a permission from ignored to allowed, it keeps defaulting back to ignored. This is a problem since the app needs all storage permissions to be enabled. Any help would be appreciated Additional context No response

📅 Opened Apr 15, 2026💬 0 comments
Quality: 30/100Contribute
Looking for more Java beginner tasks?Explore Java GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for MuntashirAkon/AppManager

When evaluating whether to contribute to MuntashirAkon/AppManager, 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 MuntashirAkon/AppManager acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to MuntashirAkon/AppManager

01

Is MuntashirAkon/AppManager welcoming to first-time open-source contributors?

MuntashirAkon/AppManager has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 7.5 C-Rank™ score represent?

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 7.5 places MuntashirAkon/AppManager in the Risky tier.

04

What is the external contributor pull request merge rate for MuntashirAkon/AppManager?

The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in MuntashirAkon/AppManager?

Yes, MuntashirAkon/AppManager currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for MuntashirAkon/AppManager 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.