Release/0.5.0 (#35)

* feat: Introduce function-scoped variable interning for state analysis with new tests and fixtures

* feat: Add Phase 26 symbolic execution enhancements with bitwise operator support, abstract interpretation refinements, and new taint analysis tests

* feat: Refine state analysis to handle factory-pattern resource returns with mixed-path tests and leak detection enhancements

* feat: Add Phase 27 debug views with symbolic execution, abstract interpretation, SSA, and call graph viewers; integrate with debug layout and styles

* feat: Add Phase 31 type-qualified symbolic resolution with receiver-based callee disambiguation and testing

* feat: Extend symbolic execution with state iteration, enhanced debug views, and debounced input handling

* feat: Add Phase 13 resource and auth pattern extensions with new tests and fixtures

* feat: Introduce CFG debug graph renderer with compact mode, toolbar, and DAG layout integration

* feat: Add Phase 28 encoding and decoding transform modeling with structural symex enhancements and new taint analysis tests

* feat: Extend abstract interpretation with type facts and constant value tracking in debug views and server logic

* feat: Add linear path handling and witness extraction to symbolic execution with Phase 28 transform mismatch detection

* feat: Refine Go auth and sanitizer handling with enhanced rules, state updates, and benchmark improvements

* feat: Enable auth-state analysis by default and update relevant tests in benchmark config

* test: Update state_tests to reflect default enablement of auth-state analysis and add auth suppression test

* docs: update CHANGELOG.md

* feat: Introduce per-index taint tracking in `HeapState` with `HeapSlot`, overflow handling, and revised SSA transfers

* feat: Introduce C/C++ language labels and refine heap state tracking in SSA transfers

* feat: Implement per-index array slot tracking in symbolic heap with overflow collapse

* feat: Add implicit definition handling for uninitialized declarations in SSA value allocation

* feat: Refactor function parameters and constants for improved clarity and maintainability

* refactor: Reorder module imports and improve formatting for consistency

* refactor: Fix formatting erorrs

* refactor: Fix clippy warnings

* refactor: Fix fmt warnings (again)

* chore: Update dependencies and improve feature configuration

* Add comprehensive tests for undertested modules (#36) (COPILOT)

* Add comprehensive tests for undertested modules

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>
Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/f3fc877e-f386-49ba-9793-fc93d3805083

* Add comprehensive tests for ext, project, walk, and errors modules

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>
Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/f3fc877e-f386-49ba-9793-fc93d3805083

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>

* chore: Update dependencies and improve feature configuration

* fix: formatting errors in new tests

* chore: Update license list in about.toml

* chore: made functions input inline

* chore: updated cfg graph to take up the full page

* chore: add Prettier configuration and update code formatting

* Add frontend test suite with Vitest (111 tests) (#37)

* Add Vitest test suite for frontend - 111 tests across utils, components, hooks, and graph utilities

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>
Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/7cf0dba2-ecff-4740-ba4d-92717e74a0b7

* ci: add frontend test step to CI workflow

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>
Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/5bc0ac9f-0a32-4d03-9cb7-7a15aea53fca

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>

* chore: simplify array initialization in test files for consistency

* ran typecheck

* feat: add AnalysisWorkspace component and integrate it into CfgViewerPage

* feat: update routing in AppLayout and improve empty state message in ExplorerPage

* feat: enhance scan progress tracking with additional metrics and stages

* feat: update license information and add license check script

* feat: implement cross-file symbolic execution with callee body persistence

* feat: replace dagre graphs with Graphology + ELK + Sigma for more advanced call stack and cfg rendering

* feat: ensure CFG function view is scoped to the selected function, preventing bleed into sibling functions

* feat: enhance resource tracking with proxy method summaries and improve finding extraction

* feat: add terminal function exit detection for accurate resource leak analysis

* feat: add warnings for loops and functions without bodies to improve error recovery

* feat: update lambda expression handling to ensure proper function classification and control flow

* feat: remove bounded formatting/string ops and add JSON.parse sanitizer for improved data handling

* feat: add inline return taint analysis and regression tests for improved security checks

* feat: add engine version management and migration handling for database schema updates

* feat: enhance first_call_ident to skip nested function bodies and add regression tests

* feat: enhance callee name resolution with two-segment normalization and disambiguation

* feat: add cross-file context flags and debug assertions for taint analysis

* feat: refactor taint analysis structure to unify context handling and improve clarity

* feat: enhance dead code elimination to preserve Sink, Source, and Sanitizer labels with new tests

* docs: updated CHANGELOG.md

* fmt: formatting fixes

* fix: fixed frontend formatting and lint warnings

* fix: optimized ci

* fix: optimized ci

* Add comprehensive multi-file test coverage to Nyx (#38)

* Initial checklist for multi-file test suite expansion

Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/e550cb88-9767-4442-94d4-101bf5bb0e23

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>

* Add 12 new multi-file test fixtures with TP/TN/near-miss coverage

Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/e550cb88-9767-4442-94d4-101bf5bb0e23

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>

* deleted root repo

* rebuilt to test for regressions

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>
Co-authored-by: elipeter <elicpeter@gmail.com>

* feat: enhance import alias resolution and taint tracking

* feat: implement security hardening with CSRF protection and path validation

* feat: add support for import alias bindings in Python, PHP, and Rust

* feat: enhance CFG analysis modes and improve code readability

* feat: add detection for parameterized SQL queries to enhance security

* feat: add safe internal redirect handling and enhance session destroy validation

* feat: implement security improvements by addressing vulnerabilities in execAsync, session management, and file downloads

* feat: enhance taint detection by adding support for inline source member expressions in call arguments

* feat: implement pre-emission of Source nodes for inline source member expressions in call arguments

* feat: add support for Throw statement in control flow and error handling

* feat: add debug and echo endpoints with potential information leakage

* feat: implement internal redirect suppression and enhance taint detection

* feat: implement module alias tracking for dynamic dispatch in JS/TS

* feat: add authorization analysis module with Express support

* feat: add authorization analysis module with Express support

* feat: add tests for admin guard requirements and clean checks in authorization analysis

* feat: integrate Koa and Fastify frameworks into authorization analysis

* feat: add Flask and Django support to authorization analysis module

* feat: add support for Rails and Sinatra frameworks in authorization analysis

* feat: add support for Axum, ActixWeb, and Rocket frameworks in authorization analysis

* feat: add support for ActixWeb, Axum, and Rocket frameworks in authorization analysis

* feat: add support for Rails and Sinatra in authorization analysis

* chore: add .DS_Store to .gitignore

* refactor: simplify conditional checks and improve readability in multiple files

* refactor: update usage of Option methods for improved clarity and consistency

* refactor: improve code readability by simplifying conditional checks and formatting

* refactor: improve code formatting and readability by simplifying conditional checks

* refactor: simplify conditional checks and improve readability in multiple files

* refactor: simplify conditional checks in axum.rs for improved readability

* feat: add CodeQL analysis configuration for enhanced security scanning

* test: add comprehensive tests for `src/output.rs` SARIF builder (#39)

* chore: start test coverage improvement work

Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/cd7ff398-134e-4728-a5e7-0353a0744423

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>

* test: add comprehensive tests for src/output.rs SARIF builder

Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/cd7ff398-134e-4728-a5e7-0353a0744423

Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>

* refactor: improve code formatting and readability in output.rs

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com>
Co-authored-by: elipeter <elicpeter@gmail.com>

* refactor: improve code formatting and readability in output.rs

* Potential fix for code scanning alert no. 210: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* Potential fix for code scanning alert no. 211: Uncontrolled data used in path expression

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* refactor: enhance triage file path handling with improved error management and validation

* refactor: updated func summaries for richer detail

* refactor: update SSA summary extraction to use canonical FuncKey for distinct entries

* refactor: enhance callee metadata structure to support arity, receiver, and qualifier for better overload resolution

* refactor: add support for keyword arguments in function calls and enhance receiver extraction for method-style calls

* refactor: implement new Flask routes for safe and unsafe shell command execution

* refactor: separate receiver handling in SSA operations and enhance taint propagation

* refactor: improve arity handling by using arg_uses for positional argument count and enhance witness scoring for tainted arguments

* refactor: implement auth decorator extraction and classification for multiple languages

* refactor: enhance Rust module path resolution and use map handling for cross-file disambiguation

* refactor: introduce CalleeQuery struct for structured callee resolution and enhance resolver logic

* refactor: implement same-file identity collision handling for `runTask` to ensure correct resolver behavior

* refactor: standardize default struct initialization across multiple files

* feat: add scripts for formatting checks and auto-fixes with test summaries

* refactor: simplify character splitting and enhance namespace qualifier handling

* refactor: improve documentation clarity and enhance code readability in resolver logic

* refactor: replace default struct initialization with explicit field assignments for clarity

* feat: enhance anonymous function naming by deriving context-based bindings

* refactor: streamline match expressions for improved readability and performance

* refactor: streamline match expressions for improved readability and performance

* refactor: replace loop with while let for improved clarity and performance

* feat: add SSA constant propagation support to analysis context for improved accuracy

* feat: add SSA constant propagation support to analysis context for improved accuracy

* feat: implement shell metacharacter validation and bounded-length checks in Rust analysis

* feat: add static map analysis for command injection suppression and type safety

* refactor: simplify match statements and reduce line breaks for improved readability

* feat(summary): phase 1/5 SinkSite data model for primary sink-location attribution

Introduce SinkSite (file_rel, line, col, snippet, cap) carrying the
primary sink source-location through function summaries. Swap
SsaFuncSummary.param_to_sink and FuncSummary.param_to_sink from a coarse
Cap map to a deduped SmallVec<[SinkSite; 1]> per parameter, with a
backward-compatible cap_sites() helper and serde defaults so pre-phase-1
on-disk rows continue to deserialise cleanly.

Extraction: SinkSiteLocator bundles the tree/bytes/file_rel needed by
extract_ssa_func_summary; ParsedFile::extract_ssa_artifacts wires the
locator in for the persisted pass-1 path, while pass-2 intra-file
transient summaries fall back to cap-only sites (behavior unchanged).
Merge: GlobalSummaries::insert now unions sink sites with
(file_rel, line, col, cap) dedup via shared union_param_sink_sites
helper.

Database: JSON-serialised summary columns carry the new shape
automatically; no schema change needed.

Phase 2 will consume SinkSite in build_taint_diag() to overwrite the
caller-site Finding.line with the callee's sink line when resolved via
summary. Phase 1 keeps behavior unchanged: scanning
tests/benchmark/corpus/rust/cmdi/cmdi_indirect.rs still produces the
same (wrong) line 10 finding.

Adds round-trip tests covering SinkSite solo, SsaFuncSummary with sink
sites, legacy-JSON default handling for both summary types, and merge
dedup.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat(taint): phase 2/5 thread SinkSite into SsaTaintEvent and Finding

Plumb Phase 1's SinkSite through the event pipeline into Findings,
no output change yet.  SsaTaintEvent gains `primary_sink_site:
Option<SinkSite>`; when the main or callback sink-emission path has
non-empty `param_to_sink_sites`, filter to sites whose
`(line != 0) && (cap ∩ sink_caps != ∅)` and emit one event per
distinct site — the multi-primary collapse keeps each downstream
Finding single-primary.

Resolution: ResolvedSummary and SinkInfo gain mirror
`param_to_sink_sites` fields, populated from `SsaFuncSummary.param_to_sink`
(SSA + callback paths) and `FuncSummary.param_to_sink` (global paths).
Label, local-summary, and interop resolution paths leave the field
empty — they only ever had cap-level info to begin with.

Finding: new `primary_location: Option<SinkLocation>` with
`file_rel/line/col`.  `ssa_events_to_findings` maps
`event.primary_sink_site` → `Finding.primary_location`, filtering
cap-only sites (`line == 0`) to `None` so the (0,0) sentinel never
leaks to formatters.  Dedup key extended with the primary location
so multi-site events aren't collapsed back together.

Invariants (debug_assert!):
* every SinkSite reaching emission has `line != 0 && cap ∩ sink_caps
  != ∅` — enforced by the pick_primary_sink_sites* filters;
* every populated Finding.primary_location has `line != 0` AND
  non-empty `file_rel` — the cap-only → None translation upstream
  guarantees this.

Deliberately independent of `uses_summary`: that flag tracks whether
the *taint chain* used a summary, whereas primary attribution
requires only that the *sink* itself was summary-resolved.  A local
source reaching a cross-file sink produces `uses_summary=false`
alongside a populated primary_location — documented on
Finding.primary_location, covered by
`cross_file_sink_finding_carries_primary_location`.

build_taint_diag, SARIF/JSON/explanation formatters, and the
benchmark scorer remain untouched: finding.line still comes from
`cfg_graph[finding.sink]`, so cmdi_indirect.rs still reports line 10
and the benchmark's rs-cmdi-003 row still shows FN in the LOC column.

Tests: `cross_file_sink_finding_carries_primary_location` (proves
plumbing via a synthetic FuncSummary carrying a SinkSite at 42:5) and
`cross_file_sink_cap_only_site_leaves_primary_location_none`
(regression guard against cap-only sites surfacing).  All 1566 lib
tests + integration tests pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* feat(output): phase 3/5 consume primary sink location in diag + SARIF

When a finding's primary_location (populated in phase 2 from a callee
summary's SinkSite) names the dangerous instruction inside a callee
body, attribute the diagnostic line to that location instead of the
caller's call site. The call site is demoted to a Call step in
flow_steps, and a synthetic Sink step at the primary location is
appended so analysts still see the full trace.

Changes:
- Add scan_root parameter to build_taint_diag so file_rel can be
  resolved back to an absolute path via a shared resolve_file_rel
  helper. Empty file_rel (single-file scans where namespace == "")
  resolves to the file under analysis.
- Extend SinkLocation with snippet, carried from the upstream
  SinkSite so the formatter needs no second file read.
- Relax the ssa_events_to_findings debug_assert to allow empty
  file_rel, which is valid when scan root equals the file itself.
- SARIF: emit data-flow as codeFlows[0].threadFlows[0].locations[];
  locations[0] already reflects the primary sink position via the
  updated diag line/col.

Acceptance: scan on tests/benchmark/corpus/rust/cmdi/cmdi_indirect.rs
now reports line 5 (Command::new) as the primary sink, with the call
site at line 10 visible in flow_steps.

Two expect.json fixtures updated (must_match line_range widened):
- javascript/taint/context_sensitive_call: 12-14 -> 7-14 (line 8 is
  the real sink inside run()).
- rust/cfg/closure_async: 10-10 -> 10-11 (line 11 is Command::new
  inside the closure).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* feat(bench): phase 4/5 validate primary sink attribution across corpus

Extend the benchmark scorer and ground truth to lock in phase 3's
primary-location behavior, and add fixtures that exercise the new
capability end-to-end.

Scorer (tests/benchmark_test.rs):
- Add optional `expected_call_site_lines: Option<Vec<[usize; 2]>>` on
  Case. When present, score_location_level additionally requires at
  least one flow_step in the finding's evidence trace to fall within
  ±2 of the call-site range. When absent, the check is skipped —
  fully forward-compatible with existing fixtures.
- Retain ±2 tolerance on expected_sink_lines (compared against the
  now-primary Diag.line post-phase-3).

Ground truth edits:
- rs-cmdi-cross-001: expected_sink_lines [8,8] -> [9,9]. Line 8 is the
  transform::wrap call site (a cross-file propagator, not a sink);
  line 9 is Command::new, the real sink. The ±2 tolerance happened to
  mask this stale attribution but it was semantically wrong — phase 4
  is the right time to correct it. Also adds expected_call_site_lines
  [8,8] so the new field is exercised on an existing cross-file case.
- rs-cmdi-003: adds expected_call_site_lines [10,10] (run_cmd call).
  This fixture's sink (Command::new inside run_cmd at line 5) was the
  motivating case for phases 1-3; adding the call-site assertion
  guards against regression to caller-line attribution.

New fixtures:
- rust/cmdi/cmdi_indirect_multisink.rs (rs-cmdi-009): helper run_both
  takes two tainted params and invokes two Command sinks on
  consecutive lines. Locks in that primary line lands inside the
  helper (lines 5-6), not at the caller (line 12). Notes document
  that SinkSite is currently one-per-callee so both findings today
  collapse onto the first sink; expected_sink_lines=[5,6] and
  expected_call_site_lines=[12,12] stay valid either way.
- python/cmdi/cross_indirect_sink/{app.py,helper.py} (py-cmdi-cross-
  004): sink os.system lives in helper.py (cross-file), caller in
  app.py reads env source and calls run_cmd. Verifies phase 3's
  cross-file primary attribution: Diag.path = helper.py, Diag.line =
  5, with app.py:7 recorded in flow_steps as a Call step.

Acceptance:
- `cargo test --test benchmark_test -- --ignored --nocapture` passes.
- rs-cmdi-003 is TP/TP/TP (the target flip FN->TP at LOC). All
  pre-existing TP/TP/TP fixtures remain TP/TP/TP; 2 new fixtures are
  TP/TP/TP.
- Aggregate rule-level: TP=158 FP=10 FN=1 TN=97, P=0.940 R=0.994
  F1=0.966 on the 266-case corpus (was TP=156 FP=10 FN=1 TN=97 on
  264 pre-phase-4, delta is the +2 new cases both resolving TP).
- Full `cargo test` green (1566 lib tests + all integration tests).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* feat(taint): phase 5/5 lock Finding.primary_location contract via regression test

Add a regression test in src/taint/ssa_transfer.rs that wires up a synthetic
SsaFuncSummary with a SinkSite at other.rs:42:10 and drives the three
emission stages (pick_primary_sink_sites → emit_ssa_taint_events →
ssa_events_to_findings) against a minimal caller SSA body.  Asserts the
resulting Finding.primary_location is exactly that triple.

The existing integration tests in src/taint/tests.rs cover the coarse
FuncSummary path end-to-end through analyse_file.  This test locks in the
lower-level SSA-side plumbing so a future refactor that silently drops the
site between pick → emit → findings fails here rather than only at the
benchmark layer.

Also refreshes tests/benchmark/results/latest.json (timestamp only; rs-cmdi-003
remains TP/TP/TP and the aggregate P/R/F1 are unchanged from phase 4).

Closes the primary sink-location attribution feature (phases 1-5/5):
* Phase 1 — SinkSite data model on summaries.
* Phase 2 — SinkSite threaded into SsaTaintEvent and Finding.
* Phase 3 — diag + SARIF consume primary_location.
* Phase 4 — benchmark validates primary_call_site_lines across corpus.
* Phase 5 — regression test locks the event→finding contract.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* refactor: clean up formatting and improve readability in multiple files

* refactor: simplify type definition for deduplication key in findings

* test(harness): add must_not_match expectation for FP regression guards

Extends ExpectedFinding with must_not_match field that asserts a
diagnostic must NOT fire — presence is a hard failure. Non-consuming
scan so it coexists with must_match entries on the same rule_id.
Adds forbidden_violations accumulator and updates summary line.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* feat(regression): update expectations to ensure must_not_match for various taint and resource leak rules

* feat: implement auto-seeding for JS/TS handler parameters to enhance taint tracking

* feat: update switch statement handling to improve control flow analysis

* feat: implement promisify alias handling for JS/TS to enhance taint tracking

* feat: enhance taint tracking by refining expectation handling and adding mode filtering

* feat: refine SQL handling in stream processing and enhance auto-seeding for handler parameters

* feat: update taint tracking rules to enforce full mode matching and improve flow analysis

* feat: enhance Ruby subshell handling to improve taint tracking and flow analysis

* feat: update xss_response expectations to refine taint flow analysis and enhance regression guarding

* feat: refine framework detection and update expectation handling for Echo and Sinatra

* feat: implement max_count for taint tracking expectations and deduplicate findings

* feat: add strict_unexpected handling for taint-unsanitised-flow in expectation files

* feat: enhance deduplication of taint-unsanitised-flow findings by collapsing based on line and severity

* feat: add strict_unexpected handling for taint-unsanitised-flow in multiple expectation files

* feat: add structural invariant checks for SSA bodies

* feat: ensure deterministic phi emission order using BTreeSet

* feat: enhance handling of terminators to ensure authoritative flow through successor edges

* feat: enhance Goto terminator handling to ensure all successors are marked executable

* feat: refactor code for improved readability and organization

* feat: simplify predicate checks and enhance readability in SSA handling

* feat: implement per-file parse timeout and enhance file size handling

* feat: migrate analysis engine toggles from environment variables to configuration file

* feat: remove unnecessary whitespace in hostile_input_tests.rs

* feat: remove unnecessary whitespace in hostile_input_tests.rs

* feat: update dependencies and enhance documentation on language maturity

* feat: enhance security headers and improve request body limits

* feat: implement sink capability bits for deduplication and enhance evidence tagging

* feat: implement dynamic activation handling for gated sinks and enhance validation logic

* feat: enhance configuration documentation and clarify inline analysis cache behavior

* feat: implement panic recovery during analysis to continue scans past errors

* feat: add expectations configuration for taint analysis and performance metrics

* feat: enhance error handling and logging during file reading and mutex locking

* feat: add cross-file body loading tests and plumbing for CF-1 phase

* feat: implement cross-file k=1 context-sensitive inline taint analysis with new tests and fixtures

* feat: implement indexed-scan parity in cross-file inline analysis with new dropdown and copy functionality

* feat: enhance classification span handling in CFG and AST for improved source attribution

* feat: add new Express routes for handling user input and telemetry data

* feat: implement ternary expression handling in CFG with diamond structure for JS/TS

* feat: implement Phase CF-3 abstract-domain transfer channels in summaries

* feat: add support for string-prefix transfer in cross-file calls and update tests

* docs: reduce RESULTS.md doc size

* feat: implement Phase CF-4 per-return-path summary decomposition with tests

* feat: update parameter handling in pass1 and refactor SsaFuncSummary initialization

* feat: implement Phase CF-5 for cross-file SCC joint fixed-point convergence with new flags and tests

* feat: implement Phase CF-6 with parameter-granularity points-to summaries and associated tests

* refactor: update comments and documentation for clarity and consistency

* style: format code for consistency and readability

* refactor: simplify verdict handling and improve edge checking logic

* refactor: optimize path and identifier collection by avoiding unnecessary cloning

* chore: update Cargo.toml for Rust version 1.85 and add ignored files; modify CHANGELOG and README for clarity on state analysis defaults

* refactor: update documentation and improve clarity in configuration files

* refactor: update documentation and improve clarity in configuration files

* feat: add JS/TS pass-2 convergence tests and expectations configuration

* feat: add Phase 5 regression tests for inline cache origin attribution and update related logic

* feat: implement Phase 7 deduplication and alternative path linking for taint findings

* feat: implement structural DFS index for anonymous functions and update naming conventions

* feat: add Phase 8 regression tests for container-element taint in JS and Python

* feat: add engine-depth profiles and explain-engine option for CLI

* feat: update expectations and add new README fixtures for multi-file scan regression

* feat: implement Phase 11 callback-alias and factory patterns with regression tests

* feat: implement Terminator::Switch for multi-way dispatch and add regression tests

* feat: add real-CVE benchmark fixtures for CVE-2023-48022, CVE-2019-14939, and CVE-2023-26159 with corresponding patched variants

* refactor: extract cfg and ssa_transfer to submodules

* refactor: cargo fmt

* refactor: remove unnecessary blank line in cfg_tests.rs

* refactor: remove unnecessary planning file

* chore: update Rust version to 1.88 and bump dependencies in Cargo files

* feat: enhance triage UI with new layout and controls, update README for clarity

* feat: enhance triage UI with new layout and controls, update README for clarity

* chore: remove outdated section from README for version 0.5.0

* docs: improve clarity and consistency in README content

* chore: add "GPL-3.0-or-later" to license options in about.toml

* chore: update license handling in about.toml and check-licenses.mjs

* style: format code for improved readability in TriagePage component

* style: format code for improved readability in TriagePage component

* chore: enhance license handling and improve body_id scoping in seed lookup

* feat: introduce owner and parent body IDs for enhanced seed scoping

* feat: implement direction-aware engine provenance with new CLI flag for strict CI gating

* feat: add Undef SSA operation for improved control-flow handling

* style: improve code formatting for consistency and readability in multiple files

* feat: add 16-function chain SCC across multiple files for enhanced analysis

* style: simplify code formatting for improved readability in multiple files

* fix: update CapHitReason default implementation and improve README clarity

* docs: enhance README with detailed explanations of taint analysis and limitations

* docs: refine README for clarity and consistency in taint analysis section

* style: improve code formatting for better readability in NewScanModal and scans

* fix: update cargo-about command to use --offline for deterministic license generation

* fix: update cargo-about command to use --offline for deterministic license generation

* ci: add step to prime cargo registry cache for deterministic license generation

* feat: add support for non-sink collections in authorization analysis

* feat: enhance authorization checks with row-level ownership equality and binding tracking

* feat: implement self-scoped user handling and enhance ownership checks

* refactor: simplify assertions and formatting in authorization analysis tests

* fix: normalize line endings in THIRDPARTY-LICENSES.html generation and update README with AI disclosure

* docs: update AI disclosure section for clarity and conciseness

* feat: add AI Contribution Policy and update contributing guidelines for AI assistance disclosure

* feat: enhance authorization analysis with SSA-derived variable type classification

* feat: implement auth_finding_to_diag function for enhanced security diagnostics

* feat: add args_value_refs to CallSite struct for enhanced argument tracking

* feat: add args_value_refs to CallSite struct for enhanced argument tracking

* feat: add direction-aware engine provenance with LossDirection classification and new CLI flag

* feat: simplify strip_cap_from_call_args call by removing unnecessary line breaks

* feat: enhance error message handling in cli_validation_tests for better Windows compatibility

* feat: optimize release profile settings in Cargo.toml and update CodeQL configuration

* feat: enhance release build process with SBOM generation and SLSA provenance

* feat: update actions/checkout and actions/setup-node to v6, enhance CLI options, and improve auth-check summaries

* feat: introduce PathFact handling for path safety checks and rejection logic

* feat: introduce PathFact handling for path safety checks and rejection logic

* feat: update benchmark data and enhance path sanitization logic with new safety checks

* feat: document AI assistance in frontend UI development and human review process

* feat: add return path facts for enhanced path safety checks and update documentation

* chore: update release date for version 0.5.0 in CHANGELOG.md

* chore: clean up ci.yml by removing outdated comments and clarifying steps

* feat: implement cross-language path sanitizers and validators for enhanced security

* feat: enhance SSA value usage tracking by including block terminators and improve path safety checks

* feat: enhance switch statement handling by adding per-case path constraints and support for exclusive cases

* refactor: simplify conditional formatting and improve code readability in executor and lower modules

* feat: add vulnerable examples for various languages demonstrating authentication and sanitization issues

* feat: enhance actor context recognition for self-actor identifiers and add support for global non-sink receivers

* feat: enhance actor context recognition for self-actor identifiers and add support for global non-sink receivers

* feat: add transform classifiers for Java, Go, and Ruby with corresponding tests

* refactor: clarify comments on reassign-to-constant idiom and sink behavior in guards.rs

---------

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

frontend/src/test/utils/findingMarkdown.test.ts

@@ -0,0 +1,188 @@
+import { describe, it, expect } from 'vitest';
+import {
+  findingToMarkdown,
+  findingsToMarkdown,
+} from '../../utils/findingMarkdown';
+import type { FindingView } from '../../api/types';
+
+const lean: FindingView = {
+  index: 0,
+  fingerprint: 'fp-lean',
+  path: 'src/a.js',
+  line: 10,
+  col: 2,
+  severity: 'High',
+  rule_id: 'js-xss',
+  category: 'xss',
+  labels: [],
+  path_validated: false,
+  suppressed: false,
+  language: 'javascript',
+  status: 'new',
+  triage_state: 'open',
+  related_findings: [],
+};
+
+const full: FindingView = {
+  index: 42,
+  fingerprint: 'fp-full-abc',
+  path: 'src/handlers/login.py',
+  line: 141,
+  col: 10,
+  severity: 'High',
+  rule_id: 'py-sqli',
+  category: 'sqli',
+  confidence: 'High',
+  rank_score: 8.7,
+  message: 'User input flows into SQL query.\nReview the construction.',
+  labels: [
+    ['source', 'request'],
+    ['sink', 'cursor.execute'],
+  ],
+  path_validated: false,
+  suppressed: false,
+  language: 'python',
+  status: 'new',
+  triage_state: 'investigating',
+  triage_note: 'Looks real — assigned to alice.',
+  code_context: {
+    start_line: 138,
+    highlight_line: 141,
+    lines: [
+      'name = request.args.get("name")',
+      '',
+      'query_name = name.strip()',
+      'cursor.execute(f"SELECT * FROM users WHERE name = \'{name}\'")',
+    ],
+  },
+  evidence: {
+    source: {
+      path: 'src/handlers/login.py',
+      line: 138,
+      col: 7,
+      kind: 'UserInput',
+      snippet: 'request.args.get("name")',
+    },
+    sink: {
+      path: 'src/handlers/login.py',
+      line: 141,
+      col: 10,
+      kind: 'SqlQuery',
+      snippet: 'cursor.execute(...)',
+    },
+    guards: [],
+    sanitizers: [],
+    notes: ['source_kind:UserInput', 'hop_count:3'],
+    flow_steps: [
+      {
+        step: 1,
+        kind: 'source',
+        file: 'src/handlers/login.py',
+        line: 138,
+        col: 7,
+        snippet: 'request.args.get("name")',
+        variable: 'name',
+      },
+      {
+        step: 2,
+        kind: 'assignment',
+        file: 'src/handlers/login.py',
+        line: 140,
+        col: 4,
+        variable: 'query_name',
+      },
+      {
+        step: 3,
+        kind: 'sink',
+        file: 'src/handlers/login.py',
+        line: 141,
+        col: 10,
+        callee: 'cursor.execute',
+        is_cross_file: true,
+      },
+    ],
+    explanation: 'Untrusted input reaches a SQL sink without sanitization.',
+    confidence_limiters: [],
+  },
+  rank_reason: [['source_kind', 'direct user input']],
+  sanitizer_status: 'none',
+  related_findings: [
+    {
+      index: 99,
+      rule_id: 'py-xss',
+      path: 'src/handlers/login.py',
+      line: 160,
+      severity: 'Medium',
+    },
+  ],
+};
+
+describe('findingToMarkdown', () => {
+  it('renders the full finding with all sections', () => {
+    const md = findingToMarkdown(full);
+    expect(md).toContain('## py-sqli — User input flows into SQL query.');
+    expect(md).toContain('- **Rule**: `py-sqli` (category: `sqli`)');
+    expect(md).toContain('- **Severity**: High | **Confidence**: High');
+    expect(md).toContain('- **Location**: `src/handlers/login.py:141:10`');
+    expect(md).toContain('- **Fingerprint**: `fp-full-abc`');
+    expect(md).toContain('- **Sanitizer status**: none');
+    expect(md).toContain('### Message\nUser input flows into SQL query.');
+    expect(md).toContain('### Explanation\nUntrusted input reaches');
+    expect(md).toContain('### Evidence');
+    expect(md).toContain(
+      '**Source** — `src/handlers/login.py:138:7` (kind: UserInput)',
+    );
+    expect(md).toContain('```python\nrequest.args.get("name")\n```');
+    expect(md).toContain('**Guards**: none');
+    expect(md).toContain('**Sanitizers**: none');
+    expect(md).toContain('### Flow (3 steps)');
+    expect(md).toContain('[cross-file]');
+    expect(md).toContain(
+      '### Code context (lines 138–141, highlight line 141)',
+    );
+    expect(md).toContain('141> ');
+    expect(md).toContain('### Labels');
+    expect(md).toContain('- `source`: `request`');
+    expect(md).toContain('### Notes');
+    expect(md).toContain('- Source type: User Input');
+    expect(md).toContain('- Path length: 3 blocks');
+    expect(md).toContain('### Triage note\nLooks real — assigned to alice.');
+    expect(md).toContain('### Confidence reasoning');
+    expect(md).toContain('Score: 8.7');
+    expect(md).toContain('- **source_kind**: direct user input');
+    expect(md).toContain('### Related findings');
+    expect(md).toContain(
+      '- `#99` `py-xss` — `src/handlers/login.py:160` (Medium)',
+    );
+  });
+
+  it('skips optional sections for a lean finding', () => {
+    const md = findingToMarkdown(lean);
+    expect(md).toContain('## js-xss — xss');
+    expect(md).toContain('**Confidence**: unknown');
+    expect(md).not.toContain('### Message');
+    expect(md).not.toContain('### Evidence');
+    expect(md).not.toContain('### Flow');
+    expect(md).not.toContain('### Code context');
+    expect(md).not.toContain('### Labels');
+    expect(md).not.toContain('### Notes');
+    expect(md).not.toContain('### Related findings');
+    expect(md).not.toContain('### Triage note');
+    expect(md).not.toContain('### Confidence reasoning');
+  });
+});
+
+describe('findingsToMarkdown', () => {
+  it('bundles multiple findings with a count header and separator', () => {
+    const md = findingsToMarkdown([full, lean]);
+    expect(md.startsWith('# Nyx findings (2)')).toBe(true);
+    expect(md).toContain('\n\n---\n\n');
+    expect(md).toContain('## py-sqli');
+    expect(md).toContain('## js-xss');
+  });
+
+  it('handles empty selection gracefully', () => {
+    const md = findingsToMarkdown([]);
+    expect(md).toBe('# Nyx findings (0)\n\n(none)');
+  });
+});

frontend/src/test/utils/formatDate.test.ts

@@ -0,0 +1,136 @@
+import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest';
+import { formatShortDate, relTime } from '../../utils/formatDate';
+
+describe('formatShortDate', () => {
+  it('returns empty string for null', () => {
+    expect(formatShortDate(null)).toBe('');
+  });
+
+  it('returns empty string for undefined', () => {
+    expect(formatShortDate(undefined)).toBe('');
+  });
+
+  it('returns empty string for empty string', () => {
+    expect(formatShortDate('')).toBe('');
+  });
+
+  it('formats a valid ISO date string with M/D H:MM pattern', () => {
+    const result = formatShortDate('2024-06-15T14:05:00.000Z');
+    expect(result).toMatch(/^\d+\/\d+ \d+:\d{2}$/);
+  });
+
+  it('zero-pads minutes to two digits', () => {
+    const d = new Date(2024, 0, 1, 10, 5, 0);
+    const result = formatShortDate(d.toISOString());
+    expect(result).toMatch(/:05$/);
+  });
+
+  it('does not zero-pad double-digit minutes', () => {
+    const d = new Date(2024, 0, 1, 10, 30, 0);
+    const result = formatShortDate(d.toISOString());
+    expect(result).toMatch(/:30$/);
+  });
+});
+
+describe('relTime', () => {
+  let now: number;
+
+  beforeEach(() => {
+    now = Date.now();
+    vi.useFakeTimers();
+    vi.setSystemTime(now);
+  });
+
+  afterEach(() => {
+    vi.useRealTimers();
+  });
+
+  it('returns empty string for null', () => {
+    expect(relTime(null)).toBe('');
+  });
+
+  it('returns empty string for undefined', () => {
+    expect(relTime(undefined)).toBe('');
+  });
+
+  it('returns empty string for empty string', () => {
+    expect(relTime('')).toBe('');
+  });
+
+  it('returns "just now" for a future date', () => {
+    const future = new Date(now + 5000).toISOString();
+    expect(relTime(future)).toBe('just now');
+  });
+
+  it('returns "just now" for 0 seconds ago', () => {
+    expect(relTime(new Date(now).toISOString())).toBe('just now');
+  });
+
+  it('returns "just now" for 1 second ago', () => {
+    expect(relTime(new Date(now - 1000).toISOString())).toBe('just now');
+  });
+
+  it('returns "Xs ago" for less than 60 seconds', () => {
+    expect(relTime(new Date(now - 30 * 1000).toISOString())).toBe('30s ago');
+  });
+
+  it('returns "1 minute ago" for exactly 60 seconds', () => {
+    expect(relTime(new Date(now - 60 * 1000).toISOString())).toBe(
+      '1 minute ago',
+    );
+  });
+
+  it('returns "X minutes ago" for less than 60 minutes', () => {
+    expect(relTime(new Date(now - 5 * 60 * 1000).toISOString())).toBe(
+      '5 minutes ago',
+    );
+  });
+
+  it('returns "1 hour ago" for exactly 1 hour', () => {
+    expect(relTime(new Date(now - 60 * 60 * 1000).toISOString())).toBe(
+      '1 hour ago',
+    );
+  });
+
+  it('returns "X hours ago" for less than 24 hours', () => {
+    expect(relTime(new Date(now - 5 * 60 * 60 * 1000).toISOString())).toBe(
+      '5 hours ago',
+    );
+  });
+
+  it('returns "1 day ago" for exactly 1 day', () => {
+    expect(relTime(new Date(now - 24 * 60 * 60 * 1000).toISOString())).toBe(
+      '1 day ago',
+    );
+  });
+
+  it('returns "X days ago" for less than 30 days', () => {
+    expect(
+      relTime(new Date(now - 10 * 24 * 60 * 60 * 1000).toISOString()),
+    ).toBe('10 days ago');
+  });
+
+  it('returns "1 month ago" for ~30 days', () => {
+    expect(
+      relTime(new Date(now - 30 * 24 * 60 * 60 * 1000).toISOString()),
+    ).toBe('1 month ago');
+  });
+
+  it('returns "X months ago" for less than 12 months', () => {
+    expect(
+      relTime(new Date(now - 6 * 30 * 24 * 60 * 60 * 1000).toISOString()),
+    ).toBe('6 months ago');
+  });
+
+  it('returns "1 year ago" for ~12 months', () => {
+    expect(
+      relTime(new Date(now - 12 * 30 * 24 * 60 * 60 * 1000).toISOString()),
+    ).toBe('1 year ago');
+  });
+
+  it('returns "X years ago" for multiple years', () => {
+    expect(
+      relTime(new Date(now - 2 * 12 * 30 * 24 * 60 * 60 * 1000).toISOString()),
+    ).toBe('2 years ago');
+  });
+});

frontend/src/test/utils/syntaxHighlight.test.ts

@@ -0,0 +1,116 @@
+import { describe, it, expect } from 'vitest';
+import { escapeHtml, highlightSyntax } from '../../utils/syntaxHighlight';
+
+describe('escapeHtml', () => {
+  it('escapes ampersands', () => {
+    expect(escapeHtml('a & b')).toBe('a & b');
+  });
+
+  it('escapes less-than signs', () => {
+    expect(escapeHtml('<div>')).toBe('&lt;div&gt;');
+  });
+
+  it('escapes greater-than signs', () => {
+    expect(escapeHtml('1 > 0')).toBe('1 &gt; 0');
+  });
+
+  it('escapes double quotes', () => {
+    expect(escapeHtml('"hello"')).toBe('&quot;hello&quot;');
+  });
+
+  it('escapes all special chars together', () => {
+    expect(escapeHtml('<a href="x&y">z</a>')).toBe(
+      '&lt;a href=&quot;x&amp;y&quot;&gt;z&lt;/a&gt;',
+    );
+  });
+
+  it('returns plain text unchanged', () => {
+    expect(escapeHtml('hello world')).toBe('hello world');
+  });
+
+  it('returns empty string unchanged', () => {
+    expect(escapeHtml('')).toBe('');
+  });
+});
+
+describe('highlightSyntax', () => {
+  it('returns input unchanged for an unknown language', () => {
+    const code = 'const x = 1;';
+    expect(highlightSyntax(code, 'cobol')).toBe(code);
+  });
+
+  it('wraps JavaScript keywords in tok-keyword spans', () => {
+    const result = highlightSyntax('const x = 1;', 'javascript');
+    expect(result).toContain('<span class="tok-keyword">const</span>');
+  });
+
+  it('wraps string literals in tok-string spans', () => {
+    const result = highlightSyntax('"hello"', 'javascript');
+    expect(result).toContain('<span class="tok-string">"hello"</span>');
+  });
+
+  it('wraps numbers in tok-number spans', () => {
+    const result = highlightSyntax('42', 'javascript');
+    expect(result).toContain('<span class="tok-number">42</span>');
+  });
+
+  it('wraps line comments in tok-comment spans', () => {
+    const result = highlightSyntax('// a comment', 'javascript');
+    expect(result).toContain('<span class="tok-comment">// a comment</span>');
+  });
+
+  it('treats typescript as a javascript alias', () => {
+    const result = highlightSyntax('const x = 1;', 'typescript');
+    expect(result).toContain('<span class="tok-keyword">const</span>');
+  });
+
+  it('highlights Python keywords', () => {
+    const result = highlightSyntax('def foo():', 'python');
+    expect(result).toContain('<span class="tok-keyword">def</span>');
+  });
+
+  it('highlights Rust keywords', () => {
+    const result = highlightSyntax('fn main()', 'rust');
+    expect(result).toContain('<span class="tok-keyword">fn</span>');
+  });
+
+  it('highlights Go keywords', () => {
+    const result = highlightSyntax('func main()', 'go');
+    expect(result).toContain('<span class="tok-keyword">func</span>');
+  });
+
+  it('highlights Java keywords', () => {
+    const result = highlightSyntax('public class Foo', 'java');
+    expect(result).toContain('<span class="tok-keyword">public</span>');
+  });
+
+  it('highlights C keywords', () => {
+    const result = highlightSyntax('int main()', 'c');
+    expect(result).toContain('<span class="tok-keyword">int</span>');
+  });
+
+  it('treats c++ as a c alias', () => {
+    const result = highlightSyntax('int x = 0;', 'c++');
+    expect(result).toContain('<span class="tok-keyword">int</span>');
+  });
+
+  it('gives comments priority over keywords inside a comment', () => {
+    const code = '// const x = 1;';
+    const result = highlightSyntax(code, 'javascript');
+    // The whole line should be a comment span, not split into keyword spans
+    expect(result).toContain(
+      '<span class="tok-comment">// const x = 1;</span>',
+    );
+    expect(result).not.toContain('tok-keyword');
+  });
+
+  it('returns unchanged text when no tokens match', () => {
+    const code = 'hello world';
+    expect(highlightSyntax(code, 'python')).toBe('hello world');
+  });
+
+  it('skips regex highlighting for very long lines', () => {
+    const code = 'const ' + 'x'.repeat(25_000);
+    expect(highlightSyntax(code, 'javascript')).toBe(code);
+  });
+});

frontend/src/test/utils/truncPath.test.ts

@@ -0,0 +1,47 @@
+import { describe, it, expect } from 'vitest';
+import { truncPath } from '../../utils/truncPath';
+
+describe('truncPath', () => {
+  it('returns empty string for null', () => {
+    expect(truncPath(null)).toBe('');
+  });
+
+  it('returns empty string for undefined', () => {
+    expect(truncPath(undefined)).toBe('');
+  });
+
+  it('returns path unchanged when shorter than maxLen', () => {
+    expect(truncPath('src/foo.ts')).toBe('src/foo.ts');
+  });
+
+  it('returns path unchanged when equal to maxLen', () => {
+    const p = 'a'.repeat(60);
+    expect(truncPath(p)).toBe(p);
+  });
+
+  it('truncates a long path with leading "..."', () => {
+    const p =
+      '/very/long/path/that/exceeds/the/default/max/length/limit/file.ts';
+    const result = truncPath(p);
+    expect(result.startsWith('...')).toBe(true);
+    expect(result.length).toBe(60);
+  });
+
+  it('keeps the tail of the path after truncation', () => {
+    const p =
+      '/very/long/path/that/exceeds/the/default/max/length/limit/file.ts';
+    const result = truncPath(p);
+    expect(result.endsWith('file.ts')).toBe(true);
+  });
+
+  it('respects a custom maxLen', () => {
+    const p = '/some/path/to/a/file.ts';
+    const result = truncPath(p, 10);
+    expect(result.length).toBe(10);
+    expect(result.startsWith('...')).toBe(true);
+  });
+
+  it('returns path unchanged when shorter than custom maxLen', () => {
+    expect(truncPath('short.ts', 20)).toBe('short.ts');
+  });
+});