apache/apr-util

0

/ 100

Documentation59
Engineering56
Health68
C84Apache-2.01d ago
Grade a repo

Getting some notice. Tests and CI would be the fastest wins.

Mirror of Apache Portable Runtime util

Documentation

59

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.

README12pt40

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

56

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

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/linux.yml).

Tests18pt80

Test files detected (test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

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)
  • 70
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 84
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 2
    Open issues
Repository files51 root entries
  • .github
    Good: CI is configured (.github/workflows/linux.yml).
  • buckets
  • buffer
  • build
  • crypto
  • dbd
  • dbm
  • docs
  • encoding
  • hooks
  • include
  • jose
  • json
  • ldap
  • memcache
  • misc
  • redis
  • strmatch
  • test
    Good: Test files detected (test).
  • uri
  • xlate
  • xml
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • apr-util.pc.in
  • aprutil.dep
  • aprutil.dsp
  • aprutil.dsw
  • aprutil.mak
  • apu-config.in
  • build.conf
  • buildconf
  • CHANGES
  • CMakeLists.txt
  • config.layout
  • configure.in
  • export_vars.sh.in
  • libaprutil.dep
  • libaprutil.dsp
  • libaprutil.mak
  • libaprutil.rc
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile.in
  • Makefile.win
  • NOTICE
  • NWGNUmakefile
  • README
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.
    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.
    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.
  • README.cmake
  • README.FREETDS
  • renames_pending
  • STATUS