85
/ 100
Polished and well engineered. Punching above its star count.
Multiplatform AWS SDK for Kotlin
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
82
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
82
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
Test files detected (aws-runtime/aws-config/common/test).
CI is configured (.github/workflows/lint.yml).
Java/Kotlin linting configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (build.gradle.kts).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 60Forks
- 734Releaseslatest 4y ago
Community
- 87% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 496Watchers
Responsiveness
- 308d 19hMedian issue response
- 1d 17hMedian PR merge time
- 66Open issues
Repository files30 root entries
- .changes
- .githubGood: CI is configured (.github/workflows/lint.yml).Good: Dependabot configured for gradle.Good: Issue or PR templates present.
- aws-runtimeGood: Test files detected (aws-runtime/aws-config/common/test).
- bom
- build-support
- buildSrc
- codegen
- docs
- dokka-aws
- examples
- gradle
- hll
- services
- tests
- .brazil-1.x.json
- .brazil.json
- .editorconfigGood: Java/Kotlin linting configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- build.gradle.ktsGood: Dependency manifest found (build.gradle.kts).
- CHANGELOG.md
- CODEOWNERS
- CONTRIBUTING.mdGood: 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.Good: Contributing guide includes code examples.
- gradle.properties
- gradlew
- gradlew.bat
- LICENSEGood: Licensed under Apache-2.0.
- NOTICE
- README.mdGood: 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.Good: README has code examples.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.Good: README documents how to install the project.Good: README documents how to run the project.
- settings.gradle.kts
- VERSIONING.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/aws/aws-sdk-kotlin)