joncampbell123/dosbox-x

0

/ 100

Documentation82
Engineering71
Health100
C3,610GPL-2.01d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

DOSBox-X fork of the DOSBox project

Documentation

82

README12pt70

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under GPL-2.0.

Engineering

71

Reproducibility6pt22

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

Tests18pt80

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (contrib/windows/launcher/dosbox-x-launcher.sln).

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)
  • 523
    Forks
  • 156
    Releaseslatest 11y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 3,610
    Watchers

Responsiveness

  • 4d 15h
    Median issue response
  • 7h
    Median PR merge time
  • 2,021
    Open issues
Repository files126 root entries
  • .github
    Good: CI is configured (.github/workflows/vsbuild_xp.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • .vscode
  • BUGS
  • build-scripts
  • chk
  • contrib
    Good: Dependency manifest found (contrib/windows/launcher/dosbox-x-launcher.sln).
  • docs
  • experiments
  • include
  • NOTES
  • NOTES-TESTING-LOG
  • OLD-REFERENCE
  • optimization-1
  • patch-integration
  • pc98-testme-1
  • ref
  • ROMs
  • scripts
  • snapshots
  • src
    Good: Licensed under GPL-2.0.
  • tests
    Good: Test files detected (tests).
  • vs
    Good: Environment pinned via vs/libpng/contrib/oss-fuzz/Dockerfile.
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • 2xscale.sh
  • acinclude.m4
  • appbundledeps.py
  • appveyor.yml
  • AUTHORS
  • autogen.sh
  • avi_zmbv_to_720p.sh
  • build
  • build_sdl1_xinput_flavor.bat
  • build_windows_installer.bat
  • build-debug
  • build-debug-g3
  • build-debug-g3-sdl2
  • build-debug-gcc-prof
  • build-debug-macos
  • build-debug-macos-sdl2
  • build-debug-os2-sdl2.cmd
  • build-debug-sdl2
  • build-debug-with-clang
  • build-emscripten-sdl2
  • build-macos
  • build-macos-sdl2
  • build-macosold
  • build-macosold-sdl2
  • build-mingw
  • build-mingw-hx-dos
  • build-mingw-lowend
  • build-mingw-lowend-sdl2
  • build-mingw-lowend9x
  • build-mingw-sdl2
  • build-mingw-sdldraw
  • build-os2-sdl2.cmd
  • build-riscos
  • build-sdl2
  • BUILD.md
  • CHANGELOG
  • cleantree
  • cleanup
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • configure.ac
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • COPYING
  • CREDITS.md
  • dos2unix.sh
  • DOSBox-Logo-2-680x350.png
  • dosbox-sdl2-diff.sh
  • dosbox-x.reference.conf
  • dosbox-x.reference.full.conf
  • dosbox224x163.png
  • dosbox224x186.png
  • dosbox224x224.png
  • dosbox224x93.png
  • dosboxpng-to-h.sh
  • Doxyfile
  • env-gcc-4.8-rpi.sh
  • env-gcc-4.8.sh
  • env-gcc-8.3.sh
  • env-gcc-8.4.sh
  • env-gcc-9.2.sh
  • env-gcc-9.3.sh
  • git-commit-version.pl
  • git-pull-mainline.sh
  • git-push-to-github.sh
  • git-setup-sdl2-work.sh
  • git-source-pickup.pl
  • git-update-all
  • git-update-all-wo-push
  • INSTALL.md
  • make-flatpak.sh
  • make-rpm.sh.in
  • make-windows-release.pl
  • Makefile.am
  • merge-dev-to-master.sh
  • merge-to-win-ci
  • MICROPHONE_IMPLEMENTATION_NOTES.md
  • mod2wav.sh
  • move-with-hist.ps1
  • mtavi2wav.sh
  • mts_to_1080p.sh
  • mts_to_2160p.sh
  • mts_to_720p.sh
  • NEWS
  • README.debugger
    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.
    Good: README documents how to run the project.
  • README.development-in-Windows
  • README.joystick
  • README.keyboard-layout-handling
  • README.md
  • README.MinGW
  • README.source-code-description
  • README.video
  • README.video-debug-overlay.md
  • README.xbrz
  • scaleup-4x3-mp4-to-1080p.sh
  • scaleup-4x3-mts-to-1080p.sh
  • SECURITY.md
    Good: Security policy present.
  • THANKS
  • TODO
  • update-build-timestamp.pl
  • update-docs-site
  • update-dosbox-x-reference-conf
  • update-en-translation
  • update-version-number