dannygriffin000/docs-travis-ci-com

0

/ 100

Documentation79
Engineering49
Health75
CSS07y ago
Grade a repo

Rough and inactive. Tests, CI, and a fuller README would revive it.

The Travis CI Documentation

Documentation

79

Contributing guide5pt5

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

49

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

Reproducibility6pt80

Lockfile present (Gemfile.lock). Installs are reproducible.

CI/CD14pt100

CI is configured (.travis.yml).

Linting and formatting5pt100

Ruby linting configured (.rubocop.yml).

Project health

75

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Dependency manifest6pt100

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files34 root entries
  • _data
  • _includes
  • _layouts
  • _plugins
  • .github
  • assets
  • images
  • legal
    Good: Security policy present.
  • newsletter
  • slate
    Good: A license file is present.
  • user
  • _config.yml
  • .alexrc
  • .coafile
  • .gitignore
    Good: .gitignore present.
  • .rubocop_todo.yml
  • .rubocop.yml
    Good: Ruby linting configured (.rubocop.yml).
  • .ruby-version
    Good: Environment pinned via .ruby-version.
  • .travis.yml
    Good: CI is configured (.travis.yml).
  • 404.html
  • CNAME
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • config.rb
  • config.ru
  • favicon.ico
  • feed.build-env-updates.xml
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • imprint.md
  • index.html
  • Procfile
  • Rakefile
  • 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.
    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.
  • STYLE.md