Some interest. A stronger README and CI would help.
Lightweight, extremely fast and memory efficient Excel output library for .NET and .NET Core applications that streams data directly to the file.
Documentation
74
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
0
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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.
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.
Project health
100
Dependency manifest found (SwiftExcel.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)
- 19Forks
- 16Releaseslatest 3y ago
Community
- —Community health
- —authors own >50% of commits
- 52Watchers
Responsiveness
- 7hMedian issue response
- 1d 12hMedian PR merge time
- 1Open issues
Repository files9 root entries
- SwiftExcel
- SwiftExcel.Sandbox
- .gitignoreGood: .gitignore present.
- key.snk
- license.mdGood: Licensed under MIT.
- logo.png
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- SwiftExcel.slnGood: Dependency manifest found (SwiftExcel.sln).
- SwiftExcel.sln.DotSettings