0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
MongoDB,RabbitMQ,DependencyInjection,WebAPI and more tools
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
93
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
62
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/build_test.yml).
Test files detected (sample/WebApi.Test.Unit/Domain/EnumKeyDicTest.cs).
Issue or PR templates present.
Project health
100
Dependency manifest found (sample/WebApi.Test.Unit/WebApi.Test.Unit.csproj).
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)
- 17Forks
- 9Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 96Watchers
Responsiveness
- 8hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/build_test.yml).Good: Dependabot covers 2 ecosystems (nuget, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .vscode
- docs
- sampleGood: Test files detected (sample/WebApi.Test.Unit/Domain/EnumKeyDicTest.cs).Good: Environment pinned via sample/WebApi.Test.Unit/Dockerfile.Good: Dependency manifest found (sample/WebApi.Test.Unit/WebApi.Test.Unit.csproj).
- src
- test
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- clear.ps1
- ClearCPM.ps1
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- Directory.Build.props
- docker-compose.basic.service.yml
- docker-compose.mongo.rs.yml
- EasilyNET.sln.DotSettings
- EasilyNET.slnx
- gitemoji.md
- LICENSEGood: Licensed under MIT.
- otel-collector-config.yaml
- Pack.ps1
- Push.ps1
- 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.
- SECURITY.mdGood: Security policy present.
- Test.ps1
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/joesdu/easilynet)