lucasg/dependencies

0

/ 100

Documentation72
Engineering58
Health75
C#11,621MIT2y ago
Grade a repo

Strong community interest, but docs and engineering haven't caught up to the hype.

A rewrite of the old legacy software "depends.exe" in C# for Windows devs to troubleshoot dll load dependencies issues.

Documentation

72

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

58

Linting and formatting5pt0

No .NET formatter configured.

→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

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.

Tests18pt80

Test files detected (test).

CI/CD14pt100

CI is configured (appveyor.yml).

Project health

75

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Dependency manifest6pt100

Dependency manifest found (Dependencies.sln).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository files14 root entries
  • ClrPhlib
  • Dependencies
  • DependenciesGui
  • DependenciesLib
  • screenshots
  • test
    Good: Test files detected (test).
  • third_party
  • .gitignore
    Good: .gitignore present.
  • appveyor.yml
    Good: CI is configured (appveyor.yml).
  • Dependencies.sln
    Good: Dependency manifest found (Dependencies.sln).
  • Deploy-Dependencies.ps1
  • LICENSE
    Good: Licensed under MIT.
  • nuget.config
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.