42
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
Repository CF Serverless untuk Indonesia
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 D (65).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
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
28
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
35
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.
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.
A test framework is installed but no test script or test files were found.
→ Add a scripts.test entry and create your first test file.
CI is configured (.github/workflows/cf.yml).
Lockfile present (bun.lockb). Installs are reproducible.
Project health
86
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)
- 1,197Forks
- 0Releases
Community
- 25% - WeakCommunity health
- -authors own >50% of commits
- 209Watchers
Responsiveness
- 19hMedian issue response
- 2d 24hMedian PR merge time
- 21Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/cf.yml).
- helper
- _worker.js
- .gitignoreGood: .gitignore present.
- bun.lockbGood: Lockfile present (bun.lockb). Installs are reproducible.
- kvProxyList.json
- package.jsonGood: Dependency manifest found (package.json).
- proxyList.txt
- rawProxyList.txt
- 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.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.
- tsconfig.json
- worker.js
- wrangler.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/foolvpn-id/nautica)