fltk/fltk
Grade a repo

0

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

FLTK - Fast Light Tool Kit - https://github.com/fltk/fltk - cross platform GUI development

Documentation76
Engineering53
Health68
C++2,228Othertoday

Documentation

76

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

53

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

CI/CD14pt40

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

Tests18pt80

Test files detected (test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 338
    Forks
  • 8
    Releaseslatest 2mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,228
    Watchers

Responsiveness

  • 6h
    Median issue response
  • 24h
    Median PR merge time
  • 73
    Open issues
Repository files56 root entries
  • .github
    Good: CI is configured (.github/workflows/build_fluid_docs.yml).
    Good: Issue or PR templates present.
  • CMake
  • documentation
    Good: Licensed under Other.
  • examples
  • FL
  • fltk-options
  • fluid
  • GL
  • jpeg
  • lib
  • libdecor
  • misc
  • nanosvg
  • package
  • png
  • public
  • screenshots
  • src
  • test
    Good: Test files detected (test).
  • util
  • zlib
  • .clang-format
  • .clang-tidy
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
  • ANNOUNCEMENT
  • CHANGES_1.0.txt
  • CHANGES_1.1.txt
  • CHANGES_1.3.txt
  • CHANGES_1.4.txt
  • CHANGES.txt
  • CMakeLists.txt
  • config.h.in
  • COPYING
  • CREDITS.txt
  • fl_config.h.in
  • fltk_version.dat
  • fltk-config.in
  • fltk.xpm
  • forms.h
  • mac_endianness.h
  • makesrcdist
  • README.abi-version.txt
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.Cairo.txt
  • README.CMake.txt
  • README.CPack.txt
  • README.documentation.txt
  • README.experimental.txt
  • README.IDE.txt
  • README.macOS.md
  • README.md
  • README.txt
  • README.Unix.txt
  • README.Wayland.txt
  • README.Windows.txt