Getting noticed, but rough fundamentals could turn visitors away.
Linux Kernel Fuzzer Corpus
Documentation
69
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.
Licensed under MIT.
Engineering
16
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
CI is configured (.github/workflows/corpusgen.yml).
Project health
59
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.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 19Forks
- 1Releaseslatest today
Community
- 37% - WeakCommunity health
- —authors own >50% of commits
- 162Watchers
Responsiveness
- 12d 2hMedian issue response
- —Median PR merge time
- 0Open issues
Repository files6 root entries
- .githubGood: CI is configured (.github/workflows/corpusgen.yml).
- files
- ci-qemu-upstream-corpus.db
- collect.py
- LICENSEGood: Licensed under MIT.
- README.mdGood: 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.