0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
CloudBase MCP - Connect CloudBase to your AI Agent. Go from AI prompt to live app.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
95
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
59
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
Test files detected (mcp/src/auth.test.ts).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/build-zips.yml).
Issue or PR templates present.
Project health
83
.gitignore present.
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 132Forks
- 31Releaseslatest 6mo ago
Community
- -Community health
- -authors own >50% of commits
- 1,036Watchers
Responsiveness
- 12hMedian issue response
- <1hMedian PR merge time
- 28Open issues
Repository files40 root entries
- .agents
- .claude
- .claude-plugin
- .codebuddyIssue: Build artifacts or local files may be committed (.codebuddy/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
- .cursor
- .githubGood: CI is configured (.github/workflows/build-zips.yml).Good: Issue or PR templates present.
- .husky
- .vscode
- .workbuddy
- config
- doc
- docs
- mcpGood: Test files detected (mcp/src/auth.test.ts).Good: Environment pinned via mcp/Dockerfile.
- plugin
- scripts
- skills
- specs
- tests
- .gitignoreGood: .gitignore present.
- .npmrc
- .versionrc
- AGENTS.md
- CHANGELOG.md
- cloudbaserc.json
- 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.
- gemini-extension.json
- glama.json
- LICENSEGood: Licensed under MIT.
- marketplace.json
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yaml
- pnpm-workspace.yaml
- README-EN.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.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.
- README-ZH.md
- README.md
- renovate.json
- tsconfig.json
- vitest.config.js
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tencentcloudbase/cloudbase-mcp)