Release v0.1.3#256
Merged
Merged
Conversation
Ship parallel absolute_risk scoring alongside frozen legacy overall, with corpus calibration, analyzer evidence emitters, and reporting across CLI, API, dashboard, and CI while defaulting to dual-score mode.
Wire min-category-score-v2 through Action and governance policy, fold scoring-v2 into main CI, validate corpus rankings at rho>=0.80, and derive pentest verdict from score_v2.risk_level when v2 is enabled.
Give developers a single entry point for dual-score mental models, CI gate cheat sheets, and accurate examples so legacy and v2 metrics are easier to find across README, getting-started, and platform/reporting docs.
Remove deprecated legacy gauge, letter grade, and terminal Legacy Index from reports when score_v2 is available so v2 is the sole visible posture signal while legacy metrics remain in JSON for CI compatibility.
Clear unused imports, line-length issues, zip(strict=), and style rules so CI ruff check passes on the v2 scoring integration branch.
Corpus p95 denominators were tiny (1–5), so high-risk scans saturated every axis at 100. Normalize dimension_scores against the scan's own peak axis so the factor radar shows which dimensions dominate.
CSS display:flex on .score-card overrode the hidden attribute, so the legacy gauge still appeared on v2 scans. Hide at render time and with !important so only the v2 absolute-risk block shows.
Restructure the overview with a hero snapshot, side-by-side issues/risk grid, and plain-language zones so v2 and legacy scans are easier to follow. Switch terminal and HTML embeds to Logo 2 assets.
Mark the attack_chains phase as skipped on prompt-only or empty tool surfaces, expose pentest_limits coverage on PentestReport, and document static-only behavior in the CLI reference.
Co-authored-by: sachinML <sachinML@users.noreply.github.com>
28 files were out of sync with ruff format; no logic changes.
Equal-height side-by-side panels with scrollable trend and risk-breakdown regions; expand scan history columns; standardize on Logo 2.jpg; update CHANGELOG.
Structured bug, feature, security, and documentation forms with type/status labels, triage checklists, and component/priority hints; sync labeling guide.
Split release (main/main_*) and integration (develop) protection with maintainer vs admin bypass actors, scoring-v2 gate, and apply script fixes.
Bump version and move Unreleased changelog entries for scoring v2 GA, dashboard overhaul, and contributor tooling shipped on develop.
| if (cs.analyzers_run) { | ||
| scoreLine += ` ${cs.analyzers_passed} of ${cs.analyzers_run} checks passed.`; | ||
| } | ||
| el.innerHTML = scoreLine; |
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.
Summary
developintomainfor v0.1.3main_0.1.2Release
0.1.3insrc/mcts/__init__.py[0.1.3] - 2026-06-12section finalizedv0.1.3after merge to trigger PyPI release workflowMade with Cursor