Solid engineering. The main gap is visibility.
Academia Sinica FAQ ChatBot
Documentation
85
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under MIT.
Engineering
51
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.
Test files detected (AS-FAQ-RAG/tests).
Lockfile present (AS-FAQ-Line-Chatbot/requirements.txt). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (AS-FAQ-Line-Chatbot/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)
- 2Forks
- 2Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 7Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 0Open issues
Repository files12 root entries
- .githubGood: Issue or PR templates present.
- AS-FAQ-Line-ChatbotGood: Lockfile present (AS-FAQ-Line-Chatbot/requirements.txt). Installs are reproducible.Good: Dependency manifest found (AS-FAQ-Line-Chatbot/requirements.txt).
- AS-FAQ-RAGGood: Test files detected (AS-FAQ-RAG/tests).Good: Environment pinned via AS-FAQ-RAG/Dockerfile.
- AS-FAQ-Web-ChatBot
- data
- .gitignoreGood: .gitignore present.
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under MIT.
- 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.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.Good: README documents how to install the project.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- Terms_of_use.md