A well-known project done right. Strong docs and solid engineering throughout.
A very fast linker for Linux
Documentation
93
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Licensed under Apache-2.0.
Engineering
87
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.
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (wild/tests).
CI is configured (.github/workflows/build-images.yml).
Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
Project health
100
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 123Forks
- 7Releaseslatest 1mo ago
Community
- —Community health
- —authors own >50% of commits
- 3,688Watchers
Responsiveness
- 7hMedian issue response
- <1hMedian PR merge time
- 72Open issues
Repository files48 root entries
- .cargo
- .githubGood: CI is configured (.github/workflows/build-images.yml).Good: Dependabot covers 2 ecosystems (github-actions, cargo). Dependencies stay current.
- .helix
- .vscode
- .zed
- benchmarks
- docker
- external_test_suites
- fakes
- fakes-debug
- images
- libwild
- linker-diff
- linker-layout
- linker-trace
- linker-utils
- nix
- wildGood: Test files detected (wild/tests).
- .dockerignore
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .gitmodules
- .typos.toml
- .yamlfmt
- BENCHMARKING.md
- cackle.toml
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- cliff.toml
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Good: Contributing guide includes code examples.
- default.nix
- DESIGN.md
- flake.lock
- flake.nix
- GOVERNANCE.md
- ld
- LICENSE-APACHE
- LICENSE-MIT
- LINKER_SCRIPT_SUPPORT.md
- PACKAGING.md
- 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.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.
- RELEASING.md
- rustfmt.tomlGood: Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
- taplo.toml
- test-config-ci.toml
- test-config.toml.sample