christianhaitian/darkos

0

/ 100

Documentation47
Engineering0
Health68
Shell6191d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

Debian based ArkOS

Documentation

47

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

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.

README12pt58

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

0

Tests18pt0

No tests detected anywhere in the repository.

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

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.

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.

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.

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)
  • 66
    Forks
  • 8
    Releaseslatest 24d ago

Community

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

Responsiveness

  • —
    Median issue response
  • 2d 3h
    Median PR merge time
  • 0
    Open issues
Repository files144 root entries
  • amiberry
  • amiga
  • audio
  • batteryplus
  • bigpemu
  • bluetooth
  • core_info_files
  • dArkOS_Tools
  • device
  • dnsmasq
  • dolphin
  • drastic
  • duckstation
  • ecwolf
  • Emulationstation
  • extra_packages
  • filebrowser
  • filecommander
  • firmware
  • flycast
  • gametank
  • global
  • gzdoom
  • hostapd
  • hotkeydaemon
  • hypseus-singe
  • inttools
  • kodi
  • launchimages
  • linapple
  • logos
  • lzdoom
  • mednafen
  • misc
  • mupen64plus
  • mvem
  • openbor
  • openmsx
  • pico8
  • piemu
  • ppsspp
  • retroarch
  • retroarch32
  • retrorun
  • scripts
  • scummvm
  • shutdownimages
  • solarus
  • ti99sim
  • xroar
  • yabasanshiro
  • .gitignore
    Good: .gitignore present.
  • bluetooth_needed_packages.txt
  • bootstrap_rootfs-rk3566.sh
  • bootstrap_rootfs.sh
  • build_351files.sh
  • build_a10mini.sh
  • build_amiberrysa.sh
  • build_applewinsa.sh
  • build_batteryplus.sh
  • build_bigpemu.sh
  • build_bluealsa.sh
  • build_controllertester.sh
  • build_deps.sh
  • build_devenv.sh
  • build_dolphinsa.sh
  • build_drastic.sh
  • build_drmtool.sh
  • build_duckstationsa.sh
  • build_ecwolfsa.sh
  • build_emulationstation-rk3566.sh
  • build_emulationstation.sh
  • build_fake08.sh
  • build_ffmpeg.sh
  • build_filebrowser.sh
  • build_filemanager.sh
  • build_flycastsa.sh
  • build_g350.sh
  • build_gametank.sh
  • build_gptokeyb.sh
  • build_gzdoom.sh
  • build_hypseus-singe.sh
  • build_image-viewer.sh
  • build_kernel-rk3566.sh
  • build_kernel.sh
  • build_kodi.sh
  • build_linapple.sh
  • build_lzdoom.sh
  • build_mednafen.sh
  • build_miniloong.sh
  • build_mupen64plussa.sh
  • build_mvem.sh
  • build_ogacontrols.sh
  • build_ogage.sh
  • build_openbor.sh
  • build_openmsxsa.sh
  • build_piemu.sh
  • build_ppsspp-2021sa.sh
  • build_ppssppsa.sh
  • build_retroarch.sh
  • build_retrorun.sh
  • build_rg351mp.sh
  • build_rg353m.sh
  • build_rg353v.sh
  • build_rg503.sh
  • build_rgb10.sh
  • build_rgb20pro.sh
  • build_rgb30.sh
  • build_rk2023.sh
  • build_scummvmsa.sh
  • build_sdl2.sh
  • build_sdljoytest.sh
  • build_solarus.sh
  • build_ti99sim.sh
  • build_wpasupplicant.sh
  • build_xroar.sh
  • build_yabasanshirosa.sh
  • clean_mounts_devenv.sh
  • clean_mounts.sh
  • cleanup_filesystem.sh
  • create_image.sh
  • fetch_compat_libs.sh
  • finishing_touches-rk3566.sh
  • finishing_touches.sh
  • FreeSudo.sh
  • game_systems.txt
  • generate_symlink.sh
  • image_setup.sh
  • kodi_needed_dev_packages.txt
  • LICENSES.md
  • Makefile
  • needed_dev_packages.txt
  • needed_packages.txt
  • needed_packages32.txt
  • prepare.sh
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    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.
  • retroarch_cores.txt
  • retroarch_cores32.txt
  • setup_partition-rk3566.sh
  • setup_partition.sh
  • standalone_kodi.sh
  • utils.sh
  • write_rootfs-rk3566.sh
  • write_rootfs.sh