Polished and well engineered. Punching above its star count.
A port of the parser from graphql-js into golang
Documentation
58
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
99
Lockfile present (go.sum). Installs are reproducible.
Test files detected (ast/argmap_test.go).
CI is configured (.github/workflows/lint.yml).
Formatting enforced (.github/.editorconfig).
Issue or PR templates present.
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)
- 139Forks
- 59Releaseslatest 6y ago
Community
- —Community health
- —authors own >50% of commits
- 559Watchers
Responsiveness
- 3hMedian issue response
- <1hMedian PR merge time
- 37Open issues
Repository files18 root entries
- .circleci
- .githubGood: CI is configured (.github/workflows/lint.yml).Good: Formatting enforced (.github/.editorconfig).Good: Dependabot covers 3 ecosystems (github-actions, gomod, npm). Dependencies stay current.Good: Issue or PR templates present.
- astGood: Test files detected (ast/argmap_test.go).
- bin
- formatter
- gqlerror
- lexer
- parser
- validator
- .gitignoreGood: .gitignore present.
- .go-version
- .golangci.yaml
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- gqlparser.go
- LICENSEGood: Licensed under MIT.
- readme.mdGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- WIP.md