Skip to content

History / Getting Started

Revisions

  • docs(wiki): document coretrace-python-analyzer 0.10.0 Ten pages, written from README, docs/usage.md, docs/plugins.md, docs/architecture.md and CHANGELOG.md: - Getting Started: install, first check, exit codes, what is and is not analysed, and why the coverage line tells 'no findings' from 'nothing analysed' - CLI Reference: every option, and why --cache/--jobs/--sbom/--vex/ --advisories/--policy need a directory check - Rules: taint flows, dangerous APIs, secrets, dependencies, plus the notes that report what could not be analysed - How a Flow is Judged: refuted / hotspot / vulnerability, what a validator proves for the kinds it declares, why a guard on another attribute is not a guard, and how attacker_arguments separate reachable from exploitable - Reports and CI: formats, the tool components naming plugins and advisory files by SHA-256, baselines, suppressions, GitHub Actions - Dependencies and Advisories: the four levels of evidence, the advisory file format, argument and semantic conditions, and what stays pending review - Plugins and Models: manifest, symbols, every model type, project_models, and what refine may not change - Architecture: the pipeline stage by stage, source layout, summaries, tests - Performance and Caching: measured cost, cache key, parallelism determinism

    @SizzleUnrlsd SizzleUnrlsd committed Sep 25, 2026