academysoftwarefoundation/openexr

0

/ 100

Documentation90
Engineering57
Health100
C1,815BSD-3-Clause1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

The OpenEXR project provides the specification and reference implementation of the EXR file format, the professional-grade image storage format of the motion picture industry.

Documentation

90

README12pt85

README is present.

Contributing guide5pt88

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under BSD-3-Clause.

Engineering

57

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.

CI/CD14pt57

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

Tests18pt80

Test files detected (src/test).

Reproducibility6pt90

Lockfile present (website/requirements.txt). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

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)
  • 693
    Forks
  • 79
    Releaseslatest 6y ago

Community

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

Responsiveness

  • 4d 18h
    Median issue response
  • <1h
    Median PR merge time
  • 95
    Open issues
Repository files32 root entries
  • .github
    Good: CI is configured (.github/workflows/ci_freebsd.yml).
    Good: Dependabot covers 4 ecosystems (github-actions, pip, gitsubmodule, bazel). Dependencies stay current.
  • ASWF
  • cmake
  • Contrib
  • docs
  • external
  • share
  • src
    Good: Test files detected (src/test).
  • website
    Good: Lockfile present (website/requirements.txt). Installs are reproducible.
  • .bazelrc
  • .bazelversion
  • .clang-format
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .readthedocs.yml
  • BUILD.bazel
  • CHANGES.md
  • CMakeLists.txt
  • CMakePresets.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    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
  • GOVERNANCE.md
  • LICENSE.md
    Good: Licensed under BSD-3-Clause.
  • MODULE.bazel
  • PATENTS
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    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.
  • SECURITY.md
    Good: Security policy present.
  • sonar-project.properties