ctrliq/ascender
Grade a repo

0

/ 100

GradeC

Good shape overall. A few tweaks would push it into the top tier.

Ascender provides a web-based user interface, REST API, and task engine built on top of Ansible. It is based off the upstream project of AWX.

Documentation55
Engineering73
Health94
Python144Apache-2.0today

Documentation

55

README12pt30

README is present.

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt77

CONTRIBUTING guide found.

License6pt100

Licensed under Apache-2.0.

Engineering

73

CI/CD14pt40

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

Tests18pt80

Test files detected (awx/conf/tests).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (awx/ui/.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 16
    Forks
  • 33
    Releaseslatest 2y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 144
    Watchers

Responsiveness

  • 21h
    Median issue response
  • <1h
    Median PR merge time
  • 9
    Open issues
Repository files27 root entries
  • .github
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/devel_images.yml).
    Good: Issue or PR templates present.
  • awx
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Test files detected (awx/conf/tests).
    Good: Linter or formatter configured (awx/ui/.prettierrc).
    Good: Environment pinned via awx/ui/Dockerfile.
  • awxkit
  • config
  • docs
  • licenses
  • requirements
  • tools
  • .coveragerc
  • .env
    Issue: Build artifacts or local files may be committed (.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • .pip-tools.toml
  • .yamllint
  • DCO_1_1.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • LICENSE.md
  • Makefile
  • manage.py
  • MANIFEST.in
  • NOTICE.txt
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • pre-commit.sh
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pytest.ini
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • setup.cfg
  • tox.ini