89
/ 100
Polished work that hasn't found its audience yet.
Intelligent Product Management Assistant - v1.0
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2License6pt
Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Reproducibility6pt
Use a multi-stage Dockerfile.
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
81
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Engineering
90
Test files detected (conftest.py).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
100
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
- 4211 / 10622Commits (30d / 90d)
- 1Forks
- 16Releaseslatest 5mo ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 5Watchers
Responsiveness
- 30d 24hMedian issue response
- <1hMedian PR merge time
- 178Open issues
Repository files90 root entries
- .claude
- .cursor
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- .pre-commit-hooks
- .serena
- .vscode
- alembic
- cli
- config
- coordination
- data
- dev
- docs
- knowledge
- logs
- mailboxes
- methodology
- metrics
- piper_morgan.egg-info
- public
- rag
- scripts
- services
- shared
- skunkworks
- suggestions
- templates
- tests
- tools
- uploads
- web
- .claude-code-rules
- .coverage
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .env.example
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mcp.json
- .native-dialog-lint-baseline.txt
- .npmrc
- .piper-backend.pid
- .piper-frontend.pid
- .pre-commit-config.yaml
- .principal-threading-baseline.txt
- .pytest-known-failures
- .python-version
- .token-lint-baseline.txt
- alembic.ini
- ba.sh
- backup_before_phase2_20251104_104652.sql
- backup_before_phase2_20251104_110227.sql
- backup_before_phase2_20251104_110245.sql
- backup_before_phase2_20251104_110300.sql
- CHANGELOG.md
- CLAUDE.md
- COMPREHENSIVE-TESTING-GUIDE.md
- conftest.pyGood: Test files detected (conftest.py).
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- CURSOR-AGENT-COMBINED-VERIFICATION.md
- DECISIONS.md
- docker-compose.staging.yml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjs
- FILE-PLACEMENT-GUIDE.md
- git.sh
- main.py
- Makefile
- next.config.ts
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pip
- postcss.config.mjs
- pyproject.toml
- pytest.ini
- 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.Good: README documents how to install the project.Good: README documents how to run the project.
- requirements.lock
- requirements.txt
- requirements.txt.bak
- robot-room.png
- screenshot.png
- secret_scanner.sh
- setup-dock-icon.sh
- SETUP.md
- start-piper.sh
- stop-piper.sh
- tailwind.config.ts
- tsconfig.json
- validate-phase5.py
- VERSION
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/mediajunkie/piper-morgan-product)