0
/ 100
Polished and well engineered. Punching above its star count.
Private control plane for AI agents
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a section showing how to install dependencies.
- 2Install and run instructions9pt
Add a section showing how to start or use the project.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Dependency manifest6pt
Add a `homepage` field pointing to your docs or project website.
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
71
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
CONTRIBUTING guide found.
README is present.
Licensed under MIT.
Engineering
98
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (apps/friday-ios/Tests).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (eslint.config.mjs).
Issue or PR templates present.
Project health
98
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)
- 118Forks
- 4Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 919Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 3Open issues
Repository files46 root entries
- .claude
- .friday-stress-fixtures
- .githooks
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.Good: Security policy present.
- appsGood: Test files detected (apps/friday-ios/Tests).
- context
- dockerGood: Environment pinned via docker/Dockerfile.
- docs
- examples
- frontend-system
- managed-skills
- memory
- packages
- packaging
- rust-core
- scripts
- skills
- src
- test
- tests
- ui
- validation
- .detect-secrets.cfg
- .dockerignore
- .env.example
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mailmap
- .secrets.baseline
- CHANGELOG.md
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- fly.toml
- Friday Setup.command
- LICENSEGood: Licensed under MIT.
- NOTICE
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yaml
- PRIVACY.md
- README.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.Good: README includes status badges.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.
- README.zh-CN.md
- RESPONSIBLE_USE.md
- ROADMAP.md
- TRUST.md
- tsconfig.json
- vitest.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/thesongzhu/friday)