8000 data: scan corpus refresh — 2026-08-30 by cloakmaster · Pull Request #44 · inkog-io/inkog · GitHub
[go: up one dir, main page]

Skip to content

data: scan corpus refresh — 2026-08-30 - #44

Open
cloakmaster wants to merge 1 commit into
mainfrom
claude/scan-corpus-2026-08-30
Open

cloakmaster wants to merge 1 commit into
mainfrom
claude/scan-corpus-2026-08-30

Conversation

@cloakmaster
@cloakmaster cloakmaster commented Aug 30, 2026 •
Copy link
Copy Markdown
Member

Scanned merlvintan/damn-vulnerable-llm-agent: 2 findings (0 CRIT, 2 HIGH, 0 MED, 0 LOW), governance score 27/100, EU AI Act readiness PARTIAL. Both findings are SQL injection via LLM-generated queries in transaction_db.py. Agent framework: LangChain.

Also adds data/scan-corpus-failures.json logging szybnev/DVLA (HTTP 400 on first attempt); merlvintan/damn-vulnerable-llm-agent was the fallback pick.

Corpus: 2 → 3 entries. Total findings observed: 9 → 11. Average governance score: 16.0 → 19.67.


Generated by Claude Code


Summary by cubic

Adds the weekly corpus scan for merlvintan/damn-vulnerable-llm-agent and logs a failed attempt for szybnev/DVLA.

  • Records 2 HIGH SQL injection findings, governance score 27/100, and PARTIAL EU AI Act readiness.
  • Updates aggregates: corpus 2→3, total findings 9→11, average governance score 16.0→19.67.
  • New data/scan-corpus-failures.json tracks the HTTP 400 from the szybnev/DVLA scan attempt.

Written for commit 3568c73. Summary will update on new commits.

Review in cubic

Add weekly scan of merlvintan/damn-vulnerable-llm-agent (2 findings,
governance 27/100). Log szybnev/DVLA as a failed attempt (HTTP 400).
Corpus grows from 2 to 3 entries; total findings observed: 11.
@cubic-dev-ai cubic-dev-ai Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:76">
P3: The new scan entry introduces a per-scan `frameworks_covered` field that no other corpus entry has and that `data/scan-corpus-readme.md` does not document in the entry structure list. Data consumers parsing scan-corpus.json now must handle a field present in one entry but absent in the other two, and its semantics are undocumented. Either add it to all entries consistently and document it in the readme, or drop it from this entry so the schema stays uniform.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread data/scan-corpus.json
"sql_injection",
"injection"
],
"frameworks_covered": ["langchain"]
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: The new scan entry introduces a per-scan frameworks_covered field that no other corpus entry has and that data/scan-corpus-readme.md does not document in the entry structure list. Data consumers parsing scan-corpus.json now must handle a field present in one entry but absent in the other two, and its semantics are undocumented. Either add it to all entries consistently and document it in the readme, or drop it from this entry so the schema stays 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 76:

<comment>The new scan entry introduces a per-scan `frameworks_covered` field that no other corpus entry has and that `data/scan-corpus-readme.md` does not document in the entry structure list. Data consumers parsing scan-corpus.json now must handle a field present in one entry but absent in the other two, and its semantics are undocumented. Either add it to all entries consistently and document it in the readme, or drop it from this entry so the schema stays uniform.</comment>

<file context>
@@ -56,6 +56,24 @@
+        "sql_injection",
+        "injection"
+      ],
+      "frameworks_covered": ["langchain"]
     }
   ]
</file context>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0