Good shape overall. A few tweaks would push it into the top tier.
Embedded Linker (eld)
Documentation
89
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under BSD-3-Clause.
Engineering
56
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 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/ci-win.yml).
Test files detected (etc/vim/test).
Lockfile present (docs/userguide/requirements.txt). Installs are reproducible.
Project health
100
Dependency manifest found (docs/userguide/requirements.txt).
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)
- 65Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 244Watchers
Responsiveness
- 11hMedian issue response
- 8hMedian PR merge time
- 223Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/ci-win.yml).Good: Dependabot configured for github-actions.
- cmake
- docsGood: Lockfile present (docs/userguide/requirements.txt). Installs are reproducible.Good: Dependency manifest found (docs/userguide/requirements.txt).
- etcGood: Test files detected (etc/vim/test).
- include
- lib
- Plugins
- presentations
- templates
- test
- tools
- utils
- .clang-format
- .clang-tidy
- .gitignoreGood: .gitignore present.
- .licenseignore
- About.md
- CHANGELOG.md
- CMakeLists.txt
- CODE-OF-CONDUCT.md
- CODEOWNERS
- configure_external_llvm.sh
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.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.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under BSD-3-Clause.
- 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.
- repolint.json
- ROADMAP.md