0
/ 100
Polished and well engineered. Punching above its star count.
A YANG-centric Go toolkit - Go/Protobuf Code Generation; Validation; Marshaling/Unmarshaling
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
91
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
83
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.
CI is configured (.github/workflows/cifuzz.yml).
Lockfile present (go.sum). Installs are reproducible.
Test files detected (demo/bgp/main_test.go).
Formatting enforced (gofmt (built into Go toolchain)).
Project health
100
Dependency manifest found (go.mod).
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)
- 121Forks
- 122Releaseslatest 6y ago
Community
- -Community health
- -authors own >50% of commits
- 326Watchers
Responsiveness
- 14d 23hMedian issue response
- 2d 1hMedian PR merge time
- 137Open issues
Repository files32 root entries
- .githubGood: CI is configured (.github/workflows/cifuzz.yml).Good: Dependabot covers 2 ecosystems (gomod, github-actions). Dependencies stay current.
- demoGood: Test files detected (demo/bgp/main_test.go).
- docs
- exampleoc
- generator
- genutil
- gnmidiff
- gogen
- integration_tests
- internal
- proto
- proto_generator
- protogen
- protomap
- testcmp
- testdata
- testutil
- uexampleoc
- util
- yangschema
- ygen
- ygot
- ypathgen
- ytypes
- .gitignoreGood: .gitignore present.
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- staticcheck.conf
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/openconfig/ygot)