Skip to content

v0.1.5

Choose a tag to compare

@Rinkia Rinkia released this 22 Jul 18:20
· 28 commits to master since this release
c9c38f0

A second lens over the same static analysis: modscan-audit maps a codebase's attack surface, and moddability reasons now carry stable IDs.

Added

  • Security Lens (modscan-audit) — a sibling command that maps a Python codebase's attack surface: where untrusted code or data can enter and execute (eval/exec, pickle/marshal/yaml deserialization, __reduce__, os.system/subprocess, dynamic loaders). Bandit-style catalog: stable MS-SEC-* ids rated by severity × confidence (separate from the moddability score), ranked most-dangerous-first. Offline, no LLM. Markdown or --json. Every report states prominently it is not a vulnerability scan — no taint, CVEs, or secrets, and an empty report is not a clean bill of health. Enumeration only; it does not trace reachability.
  • Stable IDs on moddability signals — each ranking reason carries a stable MS-MOD-* id (presentation only; score and ranking unchanged).

Full diff: v0.1.4...v0.1.5