koenderks/artsy

0

/ 100

Documentation86
Engineering58
Health68
R193GPL-3.01d ago
Grade a repo

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

aRtsy is an R package that implements algorithms for making generative art in a straightforward and standardized manner using 'ggplot2'.

Documentation

86

Contributing guide5pt30

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

58

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.

CI/CD14pt57

CI is configured (.github/workflows/lint.yaml).

Tests18pt80

Test files detected (tests).

Issue and PR templates6pt100

Issue or PR templates present.

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)
  • 21
    Forks
  • 17
    Releaseslatest 3y ago

Community

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

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files18 root entries
  • .github
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/lint.yaml).
    Good: Issue or PR templates present.
  • inst
  • man
  • png
  • R
  • src
  • tests
    Good: Test files detected (tests).
  • _pkgdown.yml
  • .gitignore
    Good: .gitignore present.
  • .lintr
  • .Rbuildignore
  • CITATION.cff
  • cran-comments.md
  • DESCRIPTION
  • LICENSE.md
    Good: Licensed under GPL-3.0.
  • NAMESPACE
  • NEWS.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    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.