Good shape overall. A few tweaks would push it into the top tier.
Pythonic file-system interface for Google Cloud Storage
Documentation
78
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under BSD-3-Clause.
Engineering
75
No linter or formatter configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
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.
Lockfile present (cloudbuild/macrobenchmarks/metrics/requirements.txt). Installs are reproducible.
Test files detected (cloudbuild/macrobenchmarks/metrics/tests).
CI is configured (.github/workflows/ci.yml).
Project health
98
Dependency manifest found (pyproject.toml).
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)
- 176Forks
- 3Releaseslatest 6d ago
Community
- —Community health
- —authors own >50% of commits
- 391Watchers
Responsiveness
- <1hMedian issue response
- 5hMedian PR merge time
- 103Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- cloudbuildGood: Test files detected (cloudbuild/macrobenchmarks/metrics/tests).Good: Lockfile present (cloudbuild/macrobenchmarks/metrics/requirements.txt). Installs are reproducible.
- docsGood: Environment pinned via docs/environment.yml.
- gcsfs
- .coveragerc
- .gitattributes
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .readthedocs.yaml
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.
- environment_gcsfs.yaml
- LICENSE.txtGood: Licensed under BSD-3-Clause.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.
- setup.cfg