0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
The Data Transfer Project makes it easy for platforms to build interoperable user data portability features. We are establishing a common framework, including data models and protocols, to enable direct transfer of data both into and out of participating online service providers.
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.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
54
README is present.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
Licensed under Apache-2.0.
Engineering
74
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.
Test files detected (client-rest/src/app/app.component.spec.ts).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/commitlint.yml).
Java/Kotlin linting configured (config/checkstyle/checkstyle.xml).
Project health
100
Dependency manifest found (build.gradle).
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)
- 494Forks
- 61Releaseslatest 6y ago
Community
- -Community health
- -authors own >50% of commits
- 3,614Watchers
Responsiveness
- 17d 18hMedian issue response
- 4hMedian PR merge time
- 37Open issues
Repository files35 root entries
- .githubGood: CI is configured (.github/workflows/commitlint.yml).Good: Dependabot configured for npm.
- client-restGood: Test files detected (client-rest/src/app/app.component.spec.ts).
- configGood: Java/Kotlin linting configured (config/checkstyle/checkstyle.xml).
- distributions
- Documentation
- extensions
- gradle
- libraries
- portability-api
- portability-api-launcher
- portability-bootstrap-vm
- portability-spi-api
- portability-spi-cloud
- portability-spi-service
- portability-spi-transfer
- portability-test-utilities
- portability-transfer
- portability-types-client
- portability-types-common
- portability-types-transfer
- scripts
- .cz.toml
- .gitattributes
- .gitignoreGood: .gitignore present.
- .travis.yml
- build.gradleGood: Dependency manifest found (build.gradle).
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.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
- LICENSEGood: Licensed under Apache-2.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- 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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.Good: README documents how to run the project.
- settings.gradle
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/dtinit/data-transfer-project)