Good community traction and solid fundamentals. Nearly in the top tier.
让 .NET 开发更简单，更通用，更流行。
Documentation
87
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
49
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 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.
Test files detected (tests).
Lockfile present (clients/schedule-dashboard/pnpm-lock.yaml). Installs are reproducible.
.NET formatting configured (framework/.editorconfig).
Project health
94
.gitignore present.
Dependency manifest found (clients/schedule-dashboard/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 470Forks
- 167Releaseslatest 5y ago
Community
- —Community health
- —authors own >50% of commits
- 2,219Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files29 root entries
- .gitee
- assets
- clientsGood: Lockfile present (clients/schedule-dashboard/pnpm-lock.yaml). Installs are reproducible.Good: Dependency manifest found (clients/schedule-dashboard/package.json).Issue: Build artifacts or local files may be committed (clients/schedule-dashboard/.env) (−40 pts).Fix: Remove them and add to .gitignore.
- frameworkGood: Licensed under Apache-2.0.Good: .NET formatting configured (framework/.editorconfig).
- references
- samples
- schemas
- snks
- templates
- testsGood: Test files detected (tests).
- tools
- .gitattributes
- .gitignoreGood: .gitignore present.
- BRANCH_MANAGEMENT.md
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- COPYRIGHT.md
- DEVELOPMENT_SETUP.md
- DISCLAIMER.md
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSE-APACHE
- LICENSE-MIT
- nuget-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.
- README.zh.md
- SECURITY.mdGood: Security policy present.
- TESTING_GUIDE.md
- 源码目录说明.md