Getting noticed, but rough fundamentals could turn visitors away.
Today I Learned
Documentation
8
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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 is present.
Engineering
40
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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 (test).
Linter or formatter configured (.prettierrc).
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 24Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 177Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 0Open issues
Repository files256 root entries
- _books
- .agent
- .claude
- agent-skill
- agentic-coding
- agile
- ai
- ai-tool
- akka
- angular
- app-store
- architecture
- asciidoc
- asset-administration-shell
- astro
- atlassian
- aws
- babel
- bitcoin
- blockchain
- blog
- cad
- ceph
- chatbot
- chrome
- claude
- clean-code
- cli
- clickhouse
- clojure
- clojurescript
- cloud
- cloudflare
- cms
- code-review
- coderabbit
- codesoom
- codex
- coding-interview
- compiler
- concurrency
- container
- cpp
- critical-errors
- crystal
- csharp
- css
- current-affairs
- cursor
- customer-service
- data
- database
- dataset
- deno
- design
- design-patterns
- design-thinking
- devops
- devrel
- distributed-system
- django
- docker
- documentation
- domain-driven-design
- domain-driven-design-quickly
- domain-specific-language
- dos
- duckdb
- electron
- elixir
- email
- ember
- envoy
- ethereum
- evernote
- fastai
- feature-flag
- figma
- floc
- flutter
- font
- fp
- framer
- frontend
- fsharp
- game
- gather-town
- gatsby
- git
- github
- gitlab
- gitops
- golang
- google
- gradle
- grafana
- graphql
- groovy
- growth-hacking
- hacker
- happy-coder
- harbor
- hardware
- haskell
- health
- heroku
- hono
- html5
- http
- identifier
- image
- ipad
- issue-tracker
- j
- java
- javascript
- jdbc
- jest
- jets
- joke
- jpa
- jujutsu
- kafka
- keycloak
- ki-editor
- kotlin
- kubernetes
- ladybird
- laravel
- learning
- linux
- liquibase
- llm
- lua
- mac
- machine-learning
- make
- management
- marko
- marp
- mcp
- megaptera
- microservices
- microsoft
- mise
- ml
- mlops
- mock-api
- multipass
- mutagen
- nestjs
- network
- nextjs
- nft
- nim
- nodejs
- obsidian
- ocaml
- oop
- opc
- open-source
- openai
- openapi
- openclaw
- opentelemetry
- orm
- parcel
- pdca
- performance
- pg
- php
- postgresql
- preact
- programming-languages
- prompt
- prototyping
- purescript
- python
- pytorch
- qrcode
- rails
- react
- react-native
- reactive
- reason
- redis
- redux
- remote-work
- rescript
- resume
- retrospective
- rollup
- roo-code
- rspack
- ruby
- rust
- scala
- scylladb
- security
- sentry
- shapeup
- sicp
- software-design-by-example
- software-engineering
- solidity
- solidjs
- spacetimedb
- spring
- sqlalchemy
- sqlite
- ssh
- ssl
- startup
- storybook
- swift
- tax
- telegram
- testGood: Test files detected (test).
- thinking
- tmux
- toss
- traefik
- twitter
- typescript
- unity
- unreal-engine
- utility
- vercel-ai
- versioning
- vim
- visual-studio-code
- visualization
- vite
- vitest
- vpn
- vue
- web
- web-api
- webassembly
- webpack
- wiki
- workflow
- working-effectively-with-legacy-code
- writing
- zapier
- zep
- zookeeper
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- AGENTS.md
- CLAUDE.md
- GEMINI.md
- README.mdGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.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.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.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.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- sandbox.md
- update_sandbox.sh