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

๐Ÿ“ฆ A versatile Scoop bucket that evolved from development tools into a comprehensive software sanctuary. Originally focused on DEV tools for applications and games, now expanded to include utilities, applications, and everyday software. Automated via GitHub CI/CD for reliable package management.

Documentation

78

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt61

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.

README12pt100

README is present.

License6pt100

Licensed under CC0-1.0.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/ci.yml).

Tests18pt80

Test files detected (test).

Reproducibility6pt92

Lockfile present (requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 1493 / 4617
    Commits (30d / 90d)
  • 34
    Forks
  • 0
    Releases

Community

  • 71% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 177
    Watchers

Responsiveness

  • 3h
    Median issue response
  • 5h
    Median PR merge time
  • 12
    Open issues
Repository files128 root entries
  • __pycache__
    Issue: Build artifacts or local files may be committed (__pycache__/AnalyzeJson.cpython-312.pyc) (โˆ’40 pts).Fix: Remove them and add to .gitignore.
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for unknown.
    Good: Issue or PR templates present.
  • .vscode
  • assets
  • bin
  • bucket
  • cache
  • carbon
  • deprecated
  • dev-sync
  • devservices
  • experiment
  • experimental
  • firefox
  • icons
  • kb
  • kibana
  • lib
  • logstash
  • misc
  • modules
  • msbuild
  • ncftp
  • non-working
  • norskord
  • not_ready
  • paintnet
  • pas2
  • rabbitmqadmin
  • removed
  • scoopmanifest
  • scripts
  • semi-working
  • slack
  • static
  • stupidgit
  • sublime-snippets
  • temp
  • templates
  • test
    Good: Test files detected (test).
  • TODO
  • uninstallers
  • updaters
  • versions
  • wip
  • .appcountbadge.json
  • .appveyor.yml
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmessage
  • .markdownlint.json
  • .mega-linter.yml
  • .pre-commit-config.yaml
  • AnalyzeJson.py
  • appveyor.yml
  • AzureSDK28.post_install.ps1
  • backup.7z
  • bash.exe.stackdump
  • bucket_backup_20260215_234206.7z
  • Bucket.Tests.ps1
  • check_https.py
  • checkdups.py
  • checkver.py
  • cleanup-manifests.py
  • 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.
    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.
  • debug.log
  • DelDupJSON.py
  • discover-versions.ps1
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • find-conflicts.py
  • find-scoopApp.ps1
  • freemind.pre_install.ps1
  • fsharp4.post_install.ps1
  • GitUpdater.jar
  • install.ps1
  • install2.ps1
  • installAsAdmin.ps1
  • ISSUE_TEMPLATE
  • java.pre_install.ps1
  • JsonFileCopy.jar
  • jsonfmt.cmd
  • jsonfmt.py
  • LICENSE
    Good: Licensed under CC0-1.0.
  • LICENSE.md
  • Makefile
  • makeindex.py
  • nlp2json.py
  • OnlyKeepJSONs.py
  • Original_Bucket_Owner.txt
  • postinstall.ps1
  • README.html
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (โˆ’45 pts).Fix: Add a section showing how to start or use the project.
  • README.md
  • remove_manifests_upon_request.py
  • RemoveDuplicates.py
  • RemoveDuplicatesBasedUponFilenames.py
  • RemoveJSONs.py
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • scoop_directory_crawler.py
  • scoop_search.py
  • Scoop-Bucket.Tests.Local.ps1
  • Scoop-Bucket.Tests.ps1
  • SearchForJSONS.ps1
  • SearchForJSONS.py
  • separate.py
  • sh.exe.stackdump
  • siggen.pre_install.ps1
  • toc.sh
  • TODO.txt
  • update-busybox.py
  • update-diskgen.py
  • update-repo.pl
  • update-windowsdesktop-runtime-lts-3.1.x.py
  • update-windowsdesktop-runtime-lts-6.0.x.py
  • update-windowsdesktop-runtime.py
  • update.py
  • updateall.py
  • Updater.ps1
  • updater.py
  • Vagrantfile
  • validate_all.cmd
  • validate.cmd
  • validate.py
  • vcredist2010.post_install.ps1
  • vcredist2015.post_install.ps1
  • WindowsSandbox.wsb
  • working_but_removed_upon_request.7z