montreux-oberland-bernois/snipe-it
Grade a repo

0

/ 100

GradeB

Solid engineering. The main gap is visibility.

Top 30% of 5,156 graded repos

A free open source IT asset/license management system

Documentation87
Engineering80
Health75
PHP0AGPL-3.06y ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  3. 3
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  4. 4
    Reproducibility6pt

    Use a multi-stage Dockerfile.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

87

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

80

Linting and formatting5pt0

No PHP linter or static analysis tool configured.

→ Add PHP_CodeSniffer (phpcs.xml) for style or PHPStan (phpstan.neon) for static analysis. Run either in CI.

Tests18pt80

Test files detected (phpunit.xml).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.travis.yml).

Issue and PR templates6pt100

Issue or PR templates present.

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 (composer.json).

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 files49 root entries
  • .github
    Good: Issue or PR templates present.
  • app
  • bootstrap
  • config
  • database
  • docker
  • public
  • resources
  • routes
  • sample_csvs
  • storage
  • tests
  • _config.yml
  • .all-contributorsrc
  • .dockerignore
  • .env.example
  • .env.testing
  • .env.testing-ci
  • .env.tests
  • .env.unit-tests
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .htaccess
  • .nvmrc
  • .travis.yml
    Good: CI is configured (.travis.yml).
  • artisan
  • bower.json
  • c3.php
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codeception.yml
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • crowdin.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.manifest
  • gh-changelog.php
  • index.html
  • install.sh
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • npm-shrinkwrap.json
  • package.json
  • phpunit.xml
    Good: Test files detected (phpunit.xml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
  • server.php
  • snipeit.sh
  • upgrade.php
  • Vagrantfile
  • webpack.mix.js
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/montreux-oberland-bernois/snipe-it)](https://www.repo-grade.com/report/montreux-oberland-bernois/snipe-it)

More graded PHP repos