juliasmoothoptimizers/krylov.jl
Grade a repo

0

/ 100

GradeF

Popular for its size, but the engineering basics lag behind the interest.

A Julia Basket of Hand-Picked Krylov Methods

Documentation58
Engineering46
Health68
Julia483Othertoday

Documentation

58

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 instructions9pt45

README documents how to install the project.

README12pt70

README is present.

License6pt100

Licensed under Other.

Engineering

46

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.

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

Tests18pt80

Test files detected (interfaces/test).

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)
  • 68
    Forks
  • 52
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 2h
    Median issue response
  • 3h
    Median PR merge time
  • 76
    Open issues
Repository files14 root entries
  • .breakage
  • .buildkite
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • benchmark
  • docs
  • interfaces
    Good: Test files detected (interfaces/test).
  • src
  • test
  • .copier-answers.jso.yml
  • .gitignore
    Good: .gitignore present.
  • CITATION.cff
  • LICENSE.md
    Good: Licensed under Other.
  • Project.toml
  • 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.
    Good: README has code examples.
    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.