Good shape overall. A few tweaks would push it into the top tier.

Aplikasi kasir (point of sales) yang dibuat menggunakan Laravel 12, Inertia 2, React dan Tailwind

Documentation

86

README12pt70

README is present.

Contributing guide5pt83

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

60

CI/CD14pt0

No CI configuration detected in this repository.

If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Reproducibility6pt70

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

Tests18pt80

Test files detected (phpunit.xml).

Linting and formatting5pt100

PHP linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (composer.json).

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)
  • 91
    Forks
  • 3
    Releaseslatest 1d ago

Community

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

Responsiveness

  • 5d 2h
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files35 root entries
  • .github
    Good: Issue or PR templates present.
  • app
  • bootstrap
  • config
  • database
  • docs
  • planning
  • public
  • resources
  • routes
  • storage
  • tests
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .htaccess
  • AGENTS.md
  • artisan
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • jsconfig.json
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
  • package.json
  • phpunit.xml
    Good: Test files detected (phpunit.xml).
  • postcss.config.js
  • 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
  • SECURITY.md
    Good: Security policy present.
  • tailwind.config.js
  • template-doc-portfolio.md
  • template-doc-portolio.md
  • vite.config.js