0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
🐻 Web UI for OpenCloud built with Vue.js and TypeScript
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (88).
See your top fixesTop 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
67
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under AGPL-3.0.
Engineering
61
Test files detected (packages/design-system/src/components/OcAvatar/OcAvatar.spec.ts).
CI is configured (.github/workflows/labels.yml).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
91
Dependency manifest found (package.json).
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)
- 45Forks
- 33Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 264Watchers
Responsiveness
- 5d 11hMedian issue response
- 3hMedian PR merge time
- 107Open issues
Repository files38 root entries
- .githubGood: CI is configured (.github/workflows/labels.yml).Good: Issue or PR templates present.
- .vscode
- config
- dev
- packagesGood: Test files detected (packages/design-system/src/components/OcAvatar/OcAvatar.spec.ts).
- patches
- polyfills
- tests
- .backportrc.json
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .prettierignore
- .prettierrc.json
- .renovaterc.json
- .woodpecker.env
- .woodpecker.star
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- cucumber.mjs
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- eslint.config.js
- gettext.config.cjs
- index.html
- LICENSEGood: Licensed under AGPL-3.0.
- Makefile
- Makefile.release
- oidc-callback.html
- oidc-silent-redirect.html
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- release-config.ts
- tsconfig.json
- vite.config.common.ts
- vite.config.ts
- web.d.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/opencloud-eu/web)