0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Ultra-lightweight native AI agent framework written entirely in Object Pascal for Delphi and Free Pascal, designed for performance, portability, and extensibility.
Documentation
86
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under MIT.
Engineering
39
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 linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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 (src/tests).
Lockfile present (cog-build-deploy/requirements.txt). Installs are reproducible.
Project health
100
Dependency manifest found (cog-build-deploy/requirements.txt).
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)
- 6Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 34Watchers
Responsiveness
- 1d 15hMedian issue response
- <1hMedian PR merge time
- 10Open issues
Repository files21 root entries
- browser
- cog
- cog-build
- cog-build-deployGood: Lockfile present (cog-build-deploy/requirements.txt). Installs are reproducible.Good: Dependency manifest found (cog-build-deploy/requirements.txt).
- cog-relay
- digitalocean
- docker
- docsGood: Contributing guide is detailed and thorough.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.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.Good: Security policy present.
- samples
- srcGood: Test files detected (src/tests).
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- build-delphi.bat
- build-fpc.bat
- CODE_REVIEW.md
- DockerfileGood: Environment pinned via Dockerfile.
- fpc.md
- LICENSEGood: Licensed under MIT.
- Makefile
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.