How Agent Pulse Is Measured
Agent Pulse is a reported source-code signal board. It is built from public git motion and The Git Reporter coverage, with caveats kept visible because the missing signals matter.
Inputs
The V0.1 snapshot reads project-owned local git caches, commit subjects, recent touched file paths, and the published article manifest. The public site receives a JSON snapshot, not the private SQLite cache.
Main Metrics
- 7d commits
- Commits whose commit date lands in the seven calendar dates ending on the snapshot date.
- Baseline delta
- Current seven-day commits minus the project's own thirty-day daily pace multiplied by seven.
- Hardening proxy
- A weighted proxy from commit subjects: fixes, tests, CI, docs, and releases. It is not a release-quality score.
- Capability tags
- Subject-line pattern hits for areas such as tools, UX, runtime, memory, permissions, security, and observability.
- Article trail
- The number of published The Git Reporter articles linked to the project in the public manifest.
Ranking Views
The page separates signal boards so raw activity does not masquerade as overall project quality.
- Most active
- Ranks by current seven-day commit count.
- Most accelerated
- Ranks by movement above the project's own thirty-day pace.
- Most hardened
- Ranks by the hardening proxy in the thirty-day window.
- Most covered
- Ranks by The Git Reporter article coverage, not external popularity.
Confidence
Confidence is a reader-facing evidence note. It rises when a repo has recent public motion, recurring article coverage, activity spread across the month, and multiple public commit authors. It does not mean the project is better or safer.
Not Collected Yet
These signals are intentionally absent until the feedback collector exists. They should not be read as zero.
Receipts
Every project row links recent commits and the latest related coverage. The raw public snapshot is available as JSON.