Repository navigation
data: scan corpus refresh — 2026-08-09 - #41
Open
cloakmaster wants to merge 1 commit into
Open
cloakmaster wants to merge 1 commit into
cloakmaster wants to merge 1 commit into
Conversation
- Add scan entry for merlvintan/damn-vulnerable-llm-agent (2 findings, governance 27/100) - Log szybnev/DVLA as failed (no_agent_code — no LLM agent code detected) - Recompute aggregates: total_scans=3, total_findings=11, avg_governance=19.67
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:81">
P3: The new scan entry adds a `frameworks_covered` field that does not exist in the two prior corpus entries and is not part of the documented per-entry schema in data/scan-corpus-readme.md. This makes the `scans` array shape inconsistent. Consumers that iterate the `scans` array expecting a uniform record shape, or that validate entries against the documented schema, will encounter a one-off, undocumented property. If this field is intentional, add it to all entries and document it; otherwise remove it to keep the corpus uniform.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| "missing_authorization", | ||
| "unbounded_loop" | ||
| ], | ||
| "frameworks_covered": ["langchain"] |
There was a problem hiding this comment.
P3: The new scan entry adds a frameworks_covered field that does not exist in the two prior corpus entries and is not part of the documented per-entry schema in data/scan-corpus-readme.md. This makes the scans array shape inconsistent. Consumers that iterate the scans array expecting a uniform record shape, or that validate entries against the documented schema, will encounter a one-off, undocumented property. If this field is intentional, add it to all entries and document it; otherwise remove it to keep the corpus uniform.
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 81:
<comment>The new scan entry adds a `frameworks_covered` field that does not exist in the two prior corpus entries and is not part of the documented per-entry schema in data/scan-corpus-readme.md. This makes the `scans` array shape inconsistent. Consumers that iterate the `scans` array expecting a uniform record shape, or that validate entries against the documented schema, will encounter a one-off, undocumented property. If this field is intentional, add it to all entries and document it; otherwise remove it to keep the corpus uniform.</comment>
<file context>
@@ -56,6 +58,27 @@
+ "missing_authorization",
+ "unbounded_loop"
+ ],
+ "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
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 (LangChain, Python): 2 findings (HIGH: 2), governance score 27/100, EU AI Act readiness PARTIAL. Both findings are SQL injection via LLM-generated queries in
transaction_db.py.First target (
szybnev/DVLA) returnedno_agent_code(HTTP 400); logged todata/scan-corpus-failures.jsonand retried with the next eligible target per protocol.Corpus is now 3 scans / 11 total findings / avg governance 19.67.
Generated by Claude Code
Summary by cubic
Refreshed the scan corpus: added a new scan for
merlvintan/damn-vulnerable-llm-agent(2 HIGH SQL injection findings, governance 27/100, EU AI Act readiness PARTIAL) and logged a failed targetszybnev/DVLA(no_agent_code). Updated aggregates to total_scans=3, total_findings=11, average_governance=19.67; addeddata/scan-corpus-failures.jsonand updateddata/scan-corpus.json.Written for commit 369464a. Summary will update on new commits.