Newborn 
HT Day-by-day study plans for Hack The Box certs: CJCA, CPTS, CWES, CWEE, CDSA, CAPE, CWPE and COAE. Pick a cert and how many hours a week you have, then check off tasks. Each tracker is one HTML file you can use online or download and run offline. Not affiliated with HTB.
https://cnmoseman.github.io/htb-study-trackers/ ↗// readme
Day-by-day study plans for Hack The Box certifications. Pick a cert, choose how many hours a week you can put in, and check off tasks as you go.
Open the site: https://cnmoseman.github.io/htb-study-trackers/
| Cert | Name | Path | Timelines |
|---|---|---|---|
| CJCA | Certified Junior Cybersecurity Associate | 20 modules, 5-day exam | 25 to 130 days |
| CPTS | Certified Penetration Testing Specialist | 28 modules, 10-day exam | 65 to 315 days |
| CWES | Certified Web Exploitation Specialist | 20 modules, 7-day exam | 30 to 150 days |
| CWEE | Certified Web Exploitation Expert | 15 modules, 10-day exam | 35 to 180 days |
| CDSA | Certified Defensive Security Analyst | 15 modules, 7-day exam | 30 to 155 days |
| CAPE | Certified Active Directory Pentesting Expert | 15 modules, 10-day exam | 45 to 225 days |
| … |
How much a project earns versus how much attention it actually gets. Above 50 means the work is outrunning its audience. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity — divided by a logarithmic reach factor.
score = signal / reach
signal = 0.25·commit_velocity // commits in last 90 days (cap 30)
+ 0.20·contributor_work // unique authors × velocity (cap 100)
+ 0.20·issue_resolution // closed ÷ total issues
+ 0.20·fork_ratio // forks ÷ stars (proxy for real usage)
+ 0.10·release_cadence // releases in 90 days (cap 3)
+ age_bonus // +0 to +0.30 after 6 months
+ homepage_bonus // +0.05 if homepage is set
reach = log₁₀(stars + watchers + 10)█ Is the project alive and maintained right now? A 0–100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.
health = 0.35·recency // days since last commit (90d decay)
+ 0.25·cadence // commit rhythm consistency
+ 0.20·issue_health // closed ÷ total issues
+ 0.20·pr_health // merged ÷ total PRs█ The colour and label on every card come straight from the health score.
Healthy 80 – 100 active, responsive, regular releases
Stable 60 – 79 maintained, steady, no alarms
Quiet 40 – 59 slowing down — watch this one
At Risk 0 – 39 going dark · candidate for rescue█ Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.
solo_builder one person holds > 80% of commits (last 180d)
needs_contributors has open "help wanted" or "good first issue" labels
hidden_gem < 100 stars · active in last 3 months · documented
legacy_hero repo > 5 years old · committed this year
fork_magnet forks/stars > 0.5 · used as template or dependency
release_machine 5+ releases in the last 90 days
under_pressure > 10 open issues · ≤ 2 contributors · health ≥ 60
community_watch watchers > stars · devs tracking before the public
community_hub GitHub Discussions enabled · > 20 discussions
funded maintainer has active funding channel█ Stars are an outcome, not effort. A project with 8 stars and daily commits is doing more interesting work than one coasting on 8k. We measure the building, then divide by the attention already received — so the genuinely undervalued rise to the top.
// stars = lagging indicator
// commits = leading indicator
// we rank by the leading one█