Repository navigation
Process execution ban and CI honesty #270
grisuno
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I closed the process-execution and CI-honesty gaps in one unit of work.
The mechanism was a category error repeated in several forms: a guard existed
in the contract but not in the enforcement surface.
os.systemwas banned inprose but still called at three sites. CI declared quality gates but swallowed
bandit, pip-audit and mypy with
|| trueandcontinue-on-error. mypy couldnot even start because installed stubs use syntax its configured interpreter
does not parse, so nobody saw the 51 errors underneath.
I generalized each fix as an executable rule rather than a one-off:
fails on a real os.system call or a manual sys.stdout assignment. Strings
that merely mention the pattern do not count.
scanner kills the mutant.
gate. Fixing the 51 errors surfaced three real bugs: an undefined yaml name,
a missing urllib.parse import, and a wrong cli.style.print_error import.
framework-intentional patterns; pip-audit reports no known vulnerabilities.
A guard that cannot run is not a guard. A gate that swallows its failure is
not a gate.
Validation: pytest 3613 passed, BDD 530 passed, mutation 11 of 11 runners
pass, ruff and mypy green, pip-audit clean.
All reactions