dtinit/data-transfer-project

0

/ 100

Documentation54
Engineering74
Health100
Java3,614Apache-2.01d ago
Grade a repo

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.

Documentation

54

README12pt35

README is present.

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt58

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.

License6pt100

Licensed under Apache-2.0.

Engineering

74

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 (client-rest/src/app/app.component.spec.ts).

Reproducibility6pt82

Lockfile present (package-lock.json). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/commitlint.yml).

Linting and formatting5pt100

Java/Kotlin linting configured (config/checkstyle/checkstyle.xml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (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)
  • 494
    Forks
  • 61
    Releaseslatest 6y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 3,614
    Watchers

Responsiveness

  • 17d 18h
    Median issue response
  • 4h
    Median PR merge time
  • 37
    Open issues
Repository files35 root entries
  • .github
    Good: CI is configured (.github/workflows/commitlint.yml).
    Good: Dependabot configured for npm.
  • client-rest
    Good: Test files detected (client-rest/src/app/app.component.spec.ts).
  • config
    Good: 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
  • .gitignore
    Good: .gitignore present.
  • .travis.yml
  • build.gradle
    Good: Dependency manifest found (build.gradle).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: 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
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • 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.
    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