Strong community interest, but docs and engineering haven't caught up to the hype.

OpenPose: Real-time multi-person keypoint detection library for body, face, hands, and foot estimation

Documentation

82

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

58

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/CD14pt57

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

Tests18pt80

Test files detected (examples/tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

47

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.

Activity5pt20

No pushes in over a year (−80 pts).

A recent commit signals the project is alive and worth contributing to.

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/main.yml).
    Good: Issue or PR templates present.
  • 3rdparty
    Good: Licensed under Other.
  • cmake
  • doc
  • examples
    Good: Test files detected (examples/tests).
  • include
  • models
  • python
  • scripts
  • src
  • .doc_autogeneration.doxygen
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • appveyor.yml
  • CMakeLists.txt
  • LICENSE
  • 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.