A well-known project done right. Strong docs and solid engineering throughout.
A library for calling C functions from Go without Cgo
Documentation
69
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 Apache-2.0.
Engineering
93
Lockfile present (go.sum). Installs are reproducible.
CI is configured (.github/workflows/test.yml).
Test files detected (callback_test.go).
Formatting enforced (gofmt (built into Go toolchain)).
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)
- 113Forks
- 11Releaseslatest 4mo ago
Community
- —Community health
- —authors own >50% of commits
- 3,676Watchers
Responsiveness
- 1hMedian issue response
- 8hMedian PR merge time
- 22Open issues
Repository files81 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Issue or PR templates present.
- cstrings
- examples
- internal
- objc
- testdata
- .gitignoreGood: .gitignore present.
- abi_amd64.h
- abi_arm64.h
- abi_loong64.h
- callback_test.goGood: Test files detected (callback_test.go).
- cdecl.go
- cgo.go
- dlerror.go
- dlfcn_android.go
- dlfcn_darwin.go
- dlfcn_freebsd.go
- dlfcn_linux.go
- dlfcn_netbsd.go
- dlfcn_nocgo_freebsd.go
- dlfcn_nocgo_linux.go
- dlfcn_nocgo_netbsd.go
- dlfcn_playground.go
- dlfcn_stubs.s
- dlfcn_test.go
- dlfcn.go
- func_test.go
- func.go
- gen.go
- go_runtime.go
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- is_ios.go
- LICENSEGood: Licensed under Apache-2.0.
- nocgo.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.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.
- struct_amd64.go
- struct_arm.go
- struct_arm64.go
- struct_loong64.go
- struct_other.go
- struct_ppc64le.go
- struct_riscv64.go
- struct_s390x.go
- struct_test.go
- sys_386.s
- sys_amd64.s
- sys_arm.s
- sys_arm64.s
- sys_loong64.s
- sys_ppc64le.s
- sys_riscv64.s
- sys_s390x.s
- sys_unix_386.s
- sys_unix_arm.s
- sys_unix_arm64.s
- sys_unix_loong64.s
- sys_unix_ppc64le.s
- sys_unix_riscv64.s
- sys_unix_s390x.s
- syscall_32bit.go
- syscall_bench_test.go
- syscall_cgo_linux.go
- syscall_linux_test.go
- syscall_notstackargs.go
- syscall_ppc64le.go
- syscall_stackargs_ppc64le.go
- syscall_stackargs_s390x.go
- syscall_test.go
- syscall_unix.go
- syscall_windows.go
- syscall.go
- wincallback.go
- zcallback_386.s
- zcallback_amd64.s
- zcallback_arm.s
- zcallback_arm64.s
- zcallback_loong64.s
- zcallback_ppc64le.s
- zcallback_riscv64.s
- zcallback_s390x.s