facebook/folly

0

/ 100

Documentation88
Engineering47
Health100
C++30,424Apache-2.05d ago
Grade a repo

Popular and well-maintained. A little polish away from elite status.

An open-source C++ library developed and used at Facebook.

Documentation

88

Contributing guide5pt66

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

47

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Reproducibility6pt12

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/oss-build-and-test.yml).

Tests18pt80

Test files detected (build/fbcode_builder/getdeps/test).

Project health

100

Dependency manifest6pt100

Dependency manifest found (folly/python/setup.py).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files22 root entries
  • .buckconfig.d
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/oss-build-and-test.yml).
    Good: Dependabot configured for devcontainers.
  • build
    Good: Test files detected (build/fbcode_builder/getdeps/test).
  • CMake
  • folly
    Good: Dependency manifest found (folly/python/setup.py).
  • static
  • .buckconfig
  • .buckroot
  • .gitignore
    Good: .gitignore present.
  • .projectid
  • BUCK
  • buck2
  • build.bat
  • build.sh
  • CMakeLists.txt
  • CMakeListsForBuck2.txt
  • 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).
    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.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • PACKAGE
  • 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.
    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.