Good shape overall. A few tweaks would push it into the top tier.
Integration to automatically fill in prices for charge data captured by TeslaMate for smart energy providers
Documentation
70
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.
README is present.
README documents how to install the project.
Licensed under MIT.
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 (TeslaMateAgile.Tests/IntegrationTests.cs).
CI is configured (.github/workflows/ci.yml).
.NET formatting configured (.editorconfig).
Project health
100
Dependency manifest found (TeslaMateAgile.Tests/TeslaMateAgile.Tests.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
- 65Releaseslatest 6y ago
Community
- —Community health
- —authors own >50% of commits
- 118Watchers
Responsiveness
- 3hMedian issue response
- 2hMedian PR merge time
- 2Open issues
Repository files15 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/ci.yml).
- .vscode
- charts
- TeslaMateAgileGood: Environment pinned via TeslaMateAgile/Dockerfile.
- TeslaMateAgile.TestsGood: Test files detected (TeslaMateAgile.Tests/IntegrationTests.cs).Good: Dependency manifest found (TeslaMateAgile.Tests/TeslaMateAgile.Tests.csproj).
- .devcontainer.json
- .dockerignore
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- Directory.Build.props
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- TeslaMateAgile.slnx