Solid engineering. The main gap is visibility.

NEO observing portal

Documentation

68

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.

README12pt65

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under GPL-3.0.

Engineering

68

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.

Tests18pt80

Test files detected (neoexchange/astrometrics/tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (Jenkinsfile).

Project health

100

Dependency manifest6pt100

Dependency manifest found (neoexchange/requirements.txt).

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)
  • 1
    Forks
  • 41
    Releaseslatest 7y ago

Community

  • Community health
  • authors own >50% of commits
  • 7
    Watchers

Responsiveness

  • 6d 9h
    Median issue response
  • 20h
    Median PR merge time
  • 77
    Open issues
Repository files10 root entries
  • docker
  • neoexchange
    Good: Test files detected (neoexchange/astrometrics/tests).
    Good: Lockfile present (neoexchange/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (neoexchange/requirements.txt).
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • INSTALL.md
  • Jenkinsfile
    Good: CI is configured (Jenkinsfile).
  • LICENSE
    Good: Licensed under GPL-3.0.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.