data: scan corpus refresh — 2026-07-05#35
Open
cloakmaster wants to merge 2 commits into
Open
Conversation
Add merlvintan/damn-vulnerable-llm-agent scan (2 findings, governance 27/100). Log szybnev/DVLA failure (no_agent_code). Recompute aggregates (3 total scans).
First attempt on szybnev/DVLA returned 400 no_agent_code; fell through to merlvintan/damn-vulnerable-llm-agent as second target per routine rules.
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="data/scan-corpus.json">
<violation number="1" location="data/scan-corpus.json:18">
P2: The `frameworks_covered` aggregate cannot be recomputed or validated from the individual `scans[]` entries because no per-scan `framework` field exists. Every other aggregate (`total_scans`, `total_findings_observed`, `average_governance_score`, `finding_categories_aggregated`) maps to fields present in each scan record. Adding a non-derivable aggregate creates silent drift risk and breaks the data-integrity contract described in the README, which says aggregates are recomputed on every refresh.
Consider adding a `framework` (or `frameworks_detected`) field to each scan entry so the aggregate is deterministic and auditable, or remove the aggregate until per-scan data is available.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| "code_injection" | ||
| ], | ||
| "last_refreshed": "2026-05-10T19:35:03Z", | ||
| "frameworks_covered": [ |
There was a problem hiding this comment.
P2: The frameworks_covered aggregate cannot be recomputed or validated from the individual scans[] entries because no per-scan framework field exists. Every other aggregate (total_scans, total_findings_observed, average_governance_score, finding_categories_aggregated) maps to fields present in each scan record. Adding a non-derivable aggregate creates silent drift risk and breaks the data-integrity contract described in the README, which says aggregates are recomputed on every refresh.
Consider adding a framework (or frameworks_detected) field to each scan entry so the aggregate is deterministic and auditable, or remove the aggregate until per-scan data is available.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At data/scan-corpus.json, line 18:
<comment>The `frameworks_covered` aggregate cannot be recomputed or validated from the individual `scans[]` entries because no per-scan `framework` field exists. Every other aggregate (`total_scans`, `total_findings_observed`, `average_governance_score`, `finding_categories_aggregated`) maps to fields present in each scan record. Adding a non-derivable aggregate creates silent drift risk and breaks the data-integrity contract described in the README, which says aggregates are recomputed on every refresh.
Consider adding a `framework` (or `frameworks_detected`) field to each scan entry so the aggregate is deterministic and auditable, or remove the aggregate until per-scan data is available.</comment>
<file context>
@@ -15,7 +15,10 @@
"code_injection"
],
- "last_refreshed": "2026-05-10T19:35:03Z",
+ "frameworks_covered": [
+ "langchain"
+ ],
</file context>
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
1 participant
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.
Scanned merlvintan/damn-vulnerable-llm-agent (2 findings, both HIGH; governance score 27/100; EU AI Act readiness: PARTIAL). Both findings are SQL injection via LLM-generated query in
transaction_db.py. Framework detected: LangChain.First attempt on
szybnev/DVLAfailed (400no_agent_code— no LLM agent code detected);scan-corpus-failures.jsoncreated to track it. Fell through tomerlvintan/damn-vulnerable-llm-agentper routine failure-handling rules.Corpus now at 3 total scans, 11 findings observed, average governance score 19.67/100.
Generated by Claude Code
Summary by cubic
Refreshes the public scan corpus with a new scan for
merlvintan/damn-vulnerable-llm-agent(2 HIGH SQL injection), updates aggregates to 3 scans/11 findings/avg governance 19.67, and addsframeworks_covered: ["langchain"]. Addsdata/scan-corpus-failures.jsonto log failed attempts and records theszybnev/DVLA400 no_agent_code event.Written for commit 641fb6a. Summary will update on new commits.