Repository navigation
feat(ai-security-context): record the scan start date and in-range total - #3833
Merged
matiasinsaurralde merged 1 commit intoNov 20, 2026
Merged
Conversation
Allow the security-context artifact to carry the scan-start-date floor the run mined to and the number of commits on or after it. The floor makes the mined depth attested, and the in-range total is the denominator for coverage within the start date, distinct from the whole-repository total — so a consumer can show both the in-range coverage and how much history the start date excludes. Both are optional, so older artifacts and full-history scans still validate. Companion to the platform scan-start-date feature (PFM-8172): the crafter and schema accept the fields; strata emits them and the control plane surfaces them in a follow-up once this is released. Signed-off-by: Matías Insaurralde <matias@chainloop.dev> Chainloop-Trace-Sessions: e5650227-b675-4bd2-8f75-eecc5f392474
Contributor
PR validation — ✅ 3 passing
AI Session Checks —
|
| Status | Policy | Messages |
|---|---|---|
| ✅ Passed | secrets-detection |
- |
✅ sast-scan
| Status | Policy | Messages |
|---|---|---|
| ✅ Passed | owasp-top10-2025 |
- |
| ✅ Passed | sast |
- |
| ✅ Passed | cwe-top25 |
- |
| ✅ Passed | cwe-top26-40-cusp |
- |
✅ iac-scan
| Status | Policy | Messages |
|---|---|---|
| ✅ Passed | iac-misconfiguration |
- |
Scans not applied (2)
| Scan | Reason |
|---|---|
vulnerability-scan |
no manifest/lockfile changed |
github-actions-scan |
no workflow files changed |
Powered by Chainloop and Chainloop Trace
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 3 files
Tip: Get a Slack DM when cubic finishes reviewing your PRs. Connect Slack
View guided diff | Re-trigger cubic
migmartri
approved these changes
Nov 19, 2026
matiasinsaurralde
marked this pull request as ready for review
November 20, 2026 13:04
matiasinsaurralde
deleted the
matias/pfm-8172-security-context-start-date
branch
November 20, 2026 13:44
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.
Allow the ai-security-context (
CHAINLOOP_AI_SECURITY_CONTEXT) artifact to carry two optional scan fields:scan_start_date: the oldest commit date the scan mined to (the backfill floor).in_range_commits_total: how many commits are on or after that date — the denominator for coverage within the start date, distinct fromrepo_commits_total(the whole repository).Both are optional, so older artifacts and full-history scans still validate. The change adds the schema properties, the crafter struct fields, and validation tests.
This is the OSS part of PFM-8172. The platform producer (strata) emits these fields and the control plane surfaces them in a paired change, once this lands in a chainloop release.
Part of https://linear.app/chainloop/issue/pfm-8172