kernelslacker/trinity

0

/ 100

Documentation39
Engineering10
Health68
C903Other1d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

Linux system call fuzzer

Documentation

39

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.

README12pt20

README is present.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

License6pt100

Licensed under Other.

Engineering

10

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.

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.

Linting and formatting5pt100

Linter or formatter configured (scripts/.flake8).

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)
  • 243
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • —
    Median issue response
  • 6h
    Median PR merge time
  • 3
    Open issues
Repository files88 root entries
  • .deps
    Good: .gitignore present.
  • childops
  • Documentation
  • fds
  • include
  • ioctls
  • lib
  • mm
  • net
  • patches
  • rand
  • scripts
    Good: Linter or formatter configured (scripts/.flake8).
  • syscalls
  • tools
  • .gitattributes
  • .gitignore
  • arg_coupling.c
  • arg-decoder.c
  • blockdevs.c
  • breadcrumb_ring.c
  • child-canary.c
  • child-capdrop-oracle.c
  • child-sentinel.c
  • child.c
  • cmp_hints.c
  • configure
  • COPYING
  • cred_throttle.c
  • csfu.c
  • debug.c
  • deferred-free.c
  • devices.c
  • fd-event.c
  • fd.c
  • fstype.c
  • futex-shared.c
  • generate-args.c
  • isolation.c
  • jsonl.c
  • kcov.c
  • kmsg-monitor.c
  • locks.c
  • log-load-bases.c
  • main.c
  • Makefile
  • minicorpus.c
  • numa.c
  • objects.c
  • output-poison.c
  • output.c
  • params.c
  • pathnames.c
  • pc_format.c
  • persist-util.c
  • pids.c
  • post-mortem.c
  • pre_crash_ring.c
  • proc-status.c
  • prop_ring.c
  • random-syscall.c
  • README
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown 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.
    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.
    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.
  • results.c
  • rlimit-safe.c
  • rlimits.c
  • self_cgroup.c
  • sequence.c
  • setup.sh
  • shm.c
  • signals-safelist.c
  • signals.c
  • spsc-ring.c
  • stats-ring.c
  • stats.c
  • strategy.c
  • struct_catalog.c
  • syscall.c
  • sysv-shm.c
  • tables-biarch.c
  • tables-uniarch.c
  • tables.c
  • taint.c
  • trinity.1
  • trinity.c
  • uid.c
  • utils.c
  • valgrind.supp
  • valresult.c
  • xattr.c