feat(telemetry): measure scan and hub export - #2812
Merged
Merged
Conversation
kevinmessiaen
marked this pull request as ready for review
September 4, 2026 03:15
henchaves
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Giskard OSS can now measure whether developers start and complete quality or vulnerability scans, and whether Checks results are prepared for Hub. These signals support the OSS vision's activation and paid-intent measures without collecting prompts, outputs, scenario content, names, paths, or arbitrary caller strings.
Caller-controlled telemetry values are constrained at runtime: modes and booleans use allowlists, requested scenario counts use fixed buckets, and scan results contain aggregate counts and duration only. This PR deliberately does not claim Scan-to-Checks conversion because OSS has no explicit promotion action that can be measured reliably.
Validation:
make checkreaches the security audit and fails on the pre-existingnltk==3.10.0advisoryPYSEC-2026-3726; the published fix is3.10.2.Related Issue
No linked issue.
Type of Change
Coding agents
The autonomous-agent instructions in
AUTONOMOUS.mdwere followed. The agent-local plan remains uncommitted.Checklist
CODE_OF_CONDUCT.mddocument.CONTRIBUTING.mdguide.uv.lockrunninguv lock(only applicable whenpyproject.tomlhas been modified)