Repository navigation
feat(vuln-scanner): verify high severity claims - #1008
Merged
Merged
Conversation
cultosagent
added a commit
to cultosagent/dogma-registry
that referenced
this pull request
Sep 1, 2026
…m Aeon root Forge exit 0 with no matching tests is not a reproduction. The SKILL examples now cd back to GITHUB_WORKSPACE and pass the clone as --repo. Co-Authored-By: Grok <grok@x.ai>
Content hash + finding line offsets for vuln-scanner SKILL.md. No new reach. Gate still fail-closed on HIGH/CRITICAL without a matching forge pass. Co-Authored-By: Grok <grok@x.ai>
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.
what
require deterministic verification before an original code finding can be published as high or critical.
needs-verificationwhy
the scanner currently allows pattern matching and manual reasoning to promote an original code finding directly to high or critical. state-dependent severity claims need reproducible evidence before disclosure.
verification
.github/workflows/ci-tests.ymlpassed locallybash scripts/tests/test_vuln_poc_gate.sh— 11/11 passedbash scripts/tests/test_skill_mode.sh— passedbash scripts/check-skill-categories.sh— passednode scripts/validate-config.js— cleaneyebrow verify --cipassedgit diff --check— cleanmutation proof: removing
env -ifrom the verifier made the poc suite exit 1 with the foundry reproduction, evidence, pinned-block, and local-verifier assertions failing. restoring it returned all 11 tests to green.real runner proof: actions run 33396274300 exercised the opt-in smoke against base at pinned block
50696537and recordedfoundry-poc=verifiedpluslive-fork-smoke foundry-fork verified. this proves the gate infrastructure ran; it does not claim that a real vulnerability was found.the integrity lock regeneration also reconciles six pre-existing stale entries on current upstream main because the repository's integrity job verifies the full tree rather than changed skills only.