Solid engineering. The main gap is visibility.
C# dependency analyzer
Documentation
65
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.
README is present.
Licensed under GPL-3.0.
Engineering
65
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.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
Test files detected (Tests).
CI is configured (.github/workflows/code-review.yml).
.NET formatting configured (.editorconfig).
Project health
100
Dependency manifest found (CSharpCodeAnalyst.sln).
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)
- 3Forks
- —Releases
Community
- 42% - WeakCommunity health
- —authors own >50% of commits
- 8Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/code-review.yml).Good: Dependabot configured for nuget.
- ApprovalTestTool
- CodeGraph
- CodeParser
- CSharpCodeAnalyst
- Documentation
- TestsGood: Test files detected (Tests).
- TestSuite
- ThirdPartyNotices
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- CLAUDE.md
- CSharpCodeAnalyst.slnGood: Dependency manifest found (CSharpCodeAnalyst.sln).
- CSharpCodeAnalyst.sln.DotSettings
- Directory.Build.props
- LICENSEGood: Licensed under GPL-3.0.
- 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.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.