0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Vlad's Playbook — the operator's field manual where every artifact is live, clickable, and forwardable. 39 chapters · 25 interactive widgets · 3 embedded case studies (AFC pitch + sanitized client audit). Read it → dive.vladyslavpodoliako.com
Documentation
89
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
30
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/deploy.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Linter or formatter configured (lint script in package.json).
Project health
92
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)
- 1Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 471Watchers
Responsiveness
- -Median issue response
- 3hMedian PR merge time
- 0Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/deploy.yml).
- apps
- assets
- docs
- public
- scripts
- src
- vault-starter
- .env.example
- .gitignoreGood: .gitignore present.
- astro.config.mjs
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Good: Contributing guide includes code examples.
- design-system.html
- LICENSEGood: Licensed under Other.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- postcss.config.cjs
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- SECURITY.mdGood: Security policy present.
- tailwind.config.ts
- tsconfig.json