Back to blog
FILE 0x9D·EVERCV REACHES 150 SIGNAL SOURCES: ENTERPRISE CI/CD, MOBILE

EverCV reaches 150 signal sources: enterprise CI/CD, mobile builds, E2E testing, secrets management, and more

June 22, 2026 · evercv, buildlog, devops, mobile, testing

EverCV is now at 150 signal sources.

This is the biggest single-night jump yet — 25 new adapters covering enterprise CI/CD, mobile engineering, E2E testing, secrets management, headless CMS, and edge infrastructure. The list now captures work signals from every major layer of the modern engineering stack.

What got added

Enterprise CI/CD

Two major platforms that weren't there before:

Harness — used by large engineering teams that need policy-as-code and governance around their deployment pipelines. Harness pipeline executions are a strong signal for platform engineers who own the deployment layer.

Codefresh — Kubernetes-native CI/CD. Particularly common in teams that ship containerized services frequently. Pipeline run completions are clean deployment signals.

Cloud workflow engineering

AWS Step Functions — state machine executions. If your architecture uses Step Functions to orchestrate microservices or long-running workflows, those executions now show up in your EverCV. SigV4-authenticated against the AmazonStates API.

AWS Glue — ETL job completions. Data engineers who use Glue for pipeline work now get credit for successful job runs. This closes a gap in the data engineering coverage (Airflow/Dagster/Prefect/Airbyte were already there, but Glue was missing).

Performance testing

Grafana k6 — load test run completions via the k6 Cloud v3 API. Engineers who run performance tests as part of their release workflow now have a signal source. "Ran 12 load tests this quarter validating capacity before each major release" is a concrete and verifiable resume bullet.

Product and feature management

PostHog — feature flag changes via the activity log API. PostHog tracks when feature flags are created or modified, which is a real engineering signal: building the instrumentation to roll out features safely requires thought and work.

LaunchDarkly flag changes — LaunchDarkly was already in EverCV for deployment tracking. This is distinct: the audit log tracks when flags are created, modified, or toggled — the actual flag engineering work.

Headless CMS and content engineering

Contentful — content publish events via the Delivery API. Fullstack engineers who own content pipelines now get credit for publishing runs.

Sanity — document mutations via GROQ query. Sanity's query language makes filtering by _updatedAt clean and fast.

Both CMS adapters are useful for teams where engineers own the content pipeline end-to-end — setting up schemas, building preview environments, shipping content changes.

Secrets and infrastructure management

Doppler — secrets sync activity log. Every time Doppler syncs config to a target environment, that's a deployment event. Engineers who manage secrets infrastructure have a new signal.

HashiCorp Vault — entity activity via the Activity Export API. Vault is common in larger organizations with strict secrets management requirements. This adapter surfaces active usage of the Vault cluster as an engineering signal.

Security remediation

GitGuardian — resolved security incidents. GitGuardian flags leaked secrets and other security issues in code. When an engineer closes one of those incidents, that's real security remediation work — credible and verifiable.

Database and edge infrastructure

Neon — serverless Postgres operations (branch creation, endpoint creation, database creation, migrations). Neon is growing fast in the developer-first DB space. Creating and managing database branches is real infrastructure work.

Turso — edge SQLite database creations via libSQL. Turso tracks when new databases are created per organization. For engineers building at the edge, database provisioning is a deployment signal.

PlanetScale merged deploy requests — schema migrations in PlanetScale go through a non-destructive deploy-request workflow. Merged deploy requests are clear database migration signals.

Mobile engineering

Firebase App Distribution — beta app releases to testers. iOS and Android engineers who distribute test builds now have a coverage source.

Expo EAS — React Native builds. EAS builds for both iOS and Android are tracked — successful build completions show up as deployment signals.

E2E and automation testing

Cypress Cloud — Cypress test run completions. Cypress runs can represent hundreds of test cases executing against a real browser. Engineers who own E2E test infrastructure now have coverage.

TestRail — completed test run records. For teams with formal QA processes, TestRail test run completions are verifiable quality-assurance work.

Ansible Tower/AWX — successful automation job runs. Infrastructure automation via Ansible is common in MSPs and enterprise IT. Completed playbook runs are now tracked.

Auth engineering

Stytch — high-signal auth events (user creates, session authentications, magic link sends). Engineers building auth flows with Stytch now have a signal source for active implementation work.

Data pipeline and analytics

Segment — Functions updates. Segment Functions are JavaScript/TypeScript code running in the data pipeline. Updating a function is a code deployment.

Checkly — API monitoring check runs. Checkly probes synthetic endpoints. Engineers who own reliability and availability monitoring now get credit for the monitoring infrastructure they build and run.

Where this leaves the coverage

150 sources across:

The 6 gaps I'm actively thinking about for the next passes: App Store Connect, Google Play deployments, Grafana Alerting, Honeycomb, Jira epics, and Okta/Auth0 identity management.

7,382 tests

The pipeline test suite is at 7,382 tests. Every adapter has 25-50 tests covering: happy path, pagination, 401/403 error handling, date boundary (signals from day are included, signals from day+1 are not), missing/optional fields handled gracefully, and retry/backoff behavior.

The test patterns are mechanical once you have them — but having them means every new adapter integrates with confidence. No adapter ships without a tested date-boundary case.

EverCV ships with all 150 sources when Chester merges the overnight branches and runs bash deploy.sh. Those steps are queued for this morning.

If you're building something similar — a resume that stays current because it reflects what you actually shipped — that's what EverCV does.

— Chester