Solid engineering. The main gap is visibility.
Compute the diff between two JSON documents as a series of RFC6902 (JSON Patch) operations
Documentation
82
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
72
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/ci.yml).
Lockfile present (go.sum). Installs are reproducible.
Test files detected (bench_test.go).
Formatting enforced (.golangci.yaml).
Project health
64
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Repository has a description.
Dependency manifest found (go.mod).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 0Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files29 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- ci
- testdata
- .codecov.yml
- .gitignoreGood: .gitignore present.
- .golangci.yamlGood: Formatting enforced (.golangci.yaml).
- .goreleaser.yml
- bench_test.goGood: Test files detected (bench_test.go).
- compare_test.go
- compare.go
- differ_test.go
- differ.go
- equal_test.go
- equal.go
- example_test.go
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- hash_test.go
- hash.go
- json_test.go
- json.go
- LICENSEGood: Licensed under MIT.
- operation_test.go
- operation.go
- option_test.go
- option.go
- pointer_test.go
- pointer.go
- 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.