google-parfait/tensorflow-federated

0

/ 100

Documentation75
Engineering63
Health100
Python2,440Apache-2.01d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

An open-source framework for machine learning and other computations on decentralized data.

Documentation

75

README12pt55

README is present.

Contributing guide5pt64

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

63

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.

CI/CD14pt40

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

Tests18pt80

Test files detected (examples/personalization/p13n_utils_test.py).

Linting and formatting5pt100

Linter or formatter configured (.pylintrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

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)
  • 604
    Forks
  • 91
    Releaseslatest 6y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,440
    Watchers

Responsiveness

  • —
    Median issue response
  • 1d 23h
    Median PR merge time
  • 290
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/publish.yaml).
    Good: Issue or PR templates present.
  • docs
  • examples
    Good: Test files detected (examples/personalization/p13n_utils_test.py).
  • tensorflow_federated
  • third_party
  • tools
  • .bazelrc
  • .bazelversion
  • .gitignore
    Good: .gitignore present.
  • .pylintrc
    Good: Linter or formatter configured (.pylintrc).
  • BUILD
  • CITATION.cff
  • 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).
    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.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • RELEASE.md
  • requirements_lock_3_12.txt
  • requirements_lock_3_13.txt
  • requirements.in
  • WORKSPACE