Repository & Ownership (.NET & Rust)
Artifacts: Git history + working tree analysis
$pulse-agent repo --guard$pulse-agent owner --lookback-months 6$pulse-agent summary --vcs-token ${GITHUB_TOKEN}Codebase · SARIF, Git bloat & ownership
Every engineering leader wants stricter static analysis, security scanning, and repository hygiene — until turning on a scanner in a mature repository dumps 4,000 existing warnings into the pipeline and developers immediately mute it.
Codebase Pulse computes deterministic fingerprints for every finding from any SARIF 2.1 tool (Roslyn, Clippy, Semgrep, Trivy, CodeQL) plus built-in Git bloat, LFS, and code ownership analyzers. Pull requests are evaluated strictly on the delta against your baseline branch: developers only see what their branch introduced or resolved.
Zero legacy warning floods
Keep thousands of historical warnings in the baseline while --guard blocks merges on new Critical findings; new warnings still show up in the PR delta.
Inline diff annotations
Pulse can upload a filtered SARIF with only new findings so GitHub Code Scanning annotations land on the exact PR line.
Beyond linters: Git & bus factor
Catch large binary commits missing Git LFS, path hygiene issues, and single-author knowledge silos in the same workflow.
PR-first workflow
Developers get credit for cleaning up legacy warnings (Resolved) and clear accountability for new findings (New Delta). And because Pulse filters the SARIF report before uploading to GitHub, inline PR comments never nag about untouched legacy code.
Rollout without friction
Start passively or pass --warn-only to post the PR report with exit code 0. Enable --guard when your team is ready to block merges on regressions.
┌────────────────────────────────────────────────────────┐ │ No new critical issues introduced in this Pull Request.│ └────────────────────────────────────────────────────────┘
┌──────────┬───────┬─────────────┬──────────┐ │ Severity │ Total │ New (Delta) │ Resolved │ ├──────────┼───────┼─────────────┼──────────┤ │ Critical │ 0 │ 0 │ 0 │ │ Warnings │ 19 │ +1 │ -2 │ │ Info │ 12 │ 0 │ -1 │ │ Total │ 31 │ +1 │ -3 │ └──────────┴───────┴─────────────┴──────────┘
┌────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Code │ Message │ ├────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ CA2007 │ Consider calling ConfigureAwait on the awaited task (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2007) │ └────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
┌─────────┬─────────────────────────────────────────────────────────────────────────┐ │ Code │ Message │ ├─────────┼─────────────────────────────────────────────────────────────────────────┤ │ CA2007 │ ConfigureAwait applied in refactored async handler on PR branch. │ │ IDE0055 │ Formatted Vue SFC script blocks with shared Prettier rules. │ │ IDE0005 │ Removed unused using directives in CodebaseEvaluationStep on PR branch. │ └─────────┴─────────────────────────────────────────────────────────────────────────┘
Under the hood
Codebase: +0 critical, +1 new warning (delta vs baseline), 3 legacy warnings resolved.
Each finding gets a stable fingerprint from rule ID, normalized path, and context so deltas survive unrelated line shifts. Guard compares the run against your baseline branch to isolate new and resolved issues, and can emit a stripped SARIF file with only new findings for native GitHub PR annotations.
Traditional audit tools sum every minor warning until a solid production codebase gets an F. Pulse caps how much hygiene noise can drag down the overall grade while treating new Critical findings as the hard gate on pull requests.
pulse-agent repo and pulse-agent owner inspect what linters miss: oversized blobs in Git history, missing .gitattributes LFS rules, cross-platform filename collisions, author concentration, orphaned modules, and bus-factor silos.
Engineering questions answered
Baseline your chosen branch as-is (no --guard). When baselines look right, run pulse-agent quality --guard on pull requests so the pipeline blocks on new Critical findings while still surfacing warning deltas in the report.
Yes. pulse-agent summary can upload a filtered SARIF that omits baseline debt and keeps only new PR findings for GitHub Code Scanning inline annotations.
pulse-agent owner analyzes Git history over a configurable lookback window to calculate bus factor, knowledge silos, and primary/secondary author distribution per directory and project.
pulse-agent repo flags large binary commits, unconfigured Git LFS extensions, and repository structure anti-patterns before they permanently bloat packfiles.
Forensic web UI
Most runs end with CI output or a PR comment. When you need to investigate a structural bottleneck, audit a release branch, or compare historical runs, open the full Codebase views in Codebase Pulse.
01 · SARIF Delta & Findings
Inspect findings from Roslyn, Clippy, Semgrep, Trivy, or custom analyzers in one unified view. Filter by scanner, rule ID, severity, or directory — and track how fast the team is burning down legacy warnings.
Zero-code on the runner
No SDK in your application. Pulse enables and reads the artifacts your toolchain already emits and uploads metadata to the product backend.
Repository & Ownership (.NET & Rust)
Artifacts: Git history + working tree analysis
$pulse-agent repo --guard$pulse-agent owner --lookback-months 6$pulse-agent summary --vcs-token ${GITHUB_TOKEN}SARIF Quality Gate (.NET & Rust)
Artifacts: Any SARIF 2.1 report (Roslyn, Clippy, Semgrep, Trivy)
$pulse-agent quality -f ./reports/analysis.sarif --guard$pulse-agent summary --vcs-token ${GITHUB_TOKEN}