googlecloudplatform/dataflowtemplates

0

/ 100

Documentation91
Engineering93
Health100
Java1,296Apache-2.01d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

Cloud Dataflow Google-provided templates for solving in-Cloud data tasks

Documentation

91

Contributing guide5pt61

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

93

Tests18pt80

Test files detected (cicd/internal/flags/common-flags_test.go).

CI/CD14pt100

CI is configured (.github/workflows/cleanup-spanner-test-infra.yml).

Linting and formatting5pt100

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

Reproducibility6pt100

Lockfile present (cicd/go.sum). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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)
  • 1,097
    Forks
  • 212
    Releaseslatest 4y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,296
    Watchers

Responsiveness

  • 19d 5h
    Median issue response
  • 14d 16h
    Median PR merge time
  • 121
    Open issues
Repository files28 root entries
  • .agents
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/cleanup-spanner-test-infra.yml).
    Good: Dependabot covers 4 ecosystems (github-actions, gomod, pip, maven). Dependencies stay current.
    Good: Issue or PR templates present.
  • .mvn
  • checkstyle
    Good: Java/Kotlin linting configured (checkstyle/checkstyle.xml).
  • cicd
    Good: Test files detected (cicd/internal/flags/common-flags_test.go).
    Good: Lockfile present (cicd/go.sum). Installs are reproducible.
  • contributor-docs
  • it
  • lt
  • metadata
  • plaintext-logging
  • plugins
  • python
    Good: Environment pinned via python/src/main/python/streaming-llm/Dockerfile.
  • structured-logging
  • test-infra
  • v1
  • v2
  • yaml
  • .gitignore
    Good: .gitignore present.
  • cloudbuild.yaml
  • 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).
    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.
  • CONTRIBUTORS.md
  • JAVA_LICENSE_HEADER
  • LICENSE
    Good: Licensed under Apache-2.0.
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.
  • session.json