googleads/googleads-mobile-android-mediation

0

/ 100

Documentation50
Engineering54
Health100
Kotlin266Apache-2.01d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Sample Android project showcasing how to build a mediation adapter or custom event for the Google Mobile Ads SDK.

Documentation

50

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt55

README is present.

Contributing guide5pt67

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

54

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt80

Test files detected (ThirdPartyAdapters/applovin/applovin/src/test).

CI/CD14pt85

CI is configured (.github/workflows/mediation_adapters.yaml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Example/app/build.gradle).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 207
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 266
    Watchers

Responsiveness

  • 2d 3h
    Median issue response
  • 8d 9h
    Median PR merge time
  • 72
    Open issues
Repository files6 root entries
  • .github
    Good: CI is configured (.github/workflows/mediation_adapters.yaml).
  • Example
    Good: Licensed under Apache-2.0.
    Good: Dependency manifest found (Example/app/build.gradle).
    Good: .gitignore present.
  • ThirdPartyAdapters
    Good: Test files detected (ThirdPartyAdapters/applovin/applovin/src/test).
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LICENSE
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.