Zero-friction setup

From install to first annotation in 10 minutes

DevPulsr works entirely within your existing GitHub or GitLab workflow. No new CI configuration, no code changes, no infrastructure to maintain.

Install now — it's free

Install GitHub App Select repos — read-only access to PRs

Open or update a PR Webhook fires automatically on every event

Analysis runs (~90s) Four passes: semantic, tests, contracts, velocity

Annotations posted to PR Inline comments in your diff — no new tab required

Review the dashboard Velocity trends update after each merge

Install with minimal permissions

DevPulsr requests read-only access to pull requests and repository structure — nothing more. No write access, no admin access, no secrets access. Installation takes 2 minutes through the GitHub Marketplace or GitLab integrations panel. You select which repositories to enable individually.

Permissions requested

Pull requests Read & write comments

Repository contents Read-only

Repository metadata Read-only

Actions / Secrets None

Admin & settings None

Install & Authorize

Analysis triggers on every PR event

As soon as a PR is opened or a commit is pushed to an existing PR, DevPulsr receives a GitHub webhook and begins analysis. The diff, changed file context, and your repo's schema files are fetched ephemerally — processed in an isolated environment, never written to persistent storage. Analysis typically completes in 45–120 seconds depending on changeset size.

→ DevPulsr analysis triggered PR #482 feat/payments-webhook Commit a4f91c2 rajsundaram ✓ Fetching diff (+47 −12 lines across 3 files) ✓ Loading schema context (api/openapi.yaml v2.1) ✓ Resolving test suite map (128 test files) Running analysis passes… ✓ Semantic pass 1.2s ✓ Test gap pass 0.8s ✓ Contract pass 0.4s ✓ Velocity pass 0.1s → Posting 3 annotations to PR… ✓ Done total: 2.6s

Annotations land inline in your diff

Findings are posted as GitHub PR review comments, attached to the specific lines they reference. Each annotation includes the finding category, severity, a plain-English explanation, and the reasoning behind it. Reviewers can respond, dismiss, or mark annotations as acknowledged — all within the normal PR flow.

auth/middleware.ts · DevPulsr annotations

31 export async function authMiddleware(req, res, next) {

32 const token = req.headers['x-auth-token'] || req.cookies.token;

Test gap: no test covers the req.cookies.token fallback path. This dual-source auth could allow a token bypass if the cookie path is less validated than the header path.

38 if (!decoded.userId) return next(createError(401));

Error propagation correct — 401 is forwarded via next() rather than thrown, consistent with this project's Express error handling convention.

Velocity dashboard updates after every merge

After a PR merges, DevPulsr updates your team's velocity metrics — PR cycle time, first-review latency, review coverage rate, and defect patterns. The dashboard is designed for engineers, not quarterly reviews: real-time data, per-engineer and per-repository breakdowns, and trend signals that flag problems while you still have time to fix them.

Velocity summary · Last 30 days

2.1h

Avg cycle time

1.4h

Time to first review

96%

Review coverage

See it on your team's PRs today

14-day free trial. Install in 10 minutes. No credit card required.

Install free on GitHub Request a GitLab demo