forcedotcom/salesforcemobilesdk-android
Grade a repo

0

/ 100

GradeC

Good shape overall. A few tweaks would push it into the top tier.

Top 38% of 5,156 graded repos

Android SDK for Salesforce

Documentation94
Engineering54
Health100
Java358Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

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.

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.

CI/CD14pt57

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

Reproducibility6pt70

Lockfile present (.github/DangerFiles/Gemfile.lock). Installs are reproducible.

Tests18pt80

Test files detected (libs/SalesforceSDK/src/com/salesforce/androidsdk/util/test).

Project health

100

Dependency manifest6pt100

Dependency manifest found (build.gradle.kts).

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)
  • 393
    Forks
  • 29
    Releaseslatest 4y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 358
    Watchers

Responsiveness

  • 9h
    Median issue response
  • 1h
    Median PR merge time
  • 18
    Open issues
Repository files32 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/nightly.yaml).
    Good: Lockfile present (.github/DangerFiles/Gemfile.lock). Installs are reproducible.
  • .prizm
  • buildSrc
  • docs
  • external
  • gradle
  • hybrid
  • libs
    Good: Test files detected (libs/SalesforceSDK/src/com/salesforce/androidsdk/util/test).
  • native
  • publish
  • shared
  • tools
  • .codecov.yml
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • build.gradle.kts
    Good: Dependency manifest found (build.gradle.kts).
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • 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.
    Good: Contributing guide explains how to run tests.
    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.
  • gradle.properties
  • gradlew
  • gradlew.bat
  • install.sh
  • install.vbs
  • LICENSE.md
    Good: Licensed under Other.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • settings.gradle.kts
  • setversion.sh
  • UPGRADE.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/forcedotcom/salesforcemobilesdk-android)](https://www.repo-grade.com/report/forcedotcom/salesforcemobilesdk-android)

More graded Java repos