Skip to content

stability: implement audit findings remediation plan - #38

Merged
tonyredondo merged 8 commits into
mainfrom
fix/audit-findings-hardening-2026-02
Feb 20, 2026
Merged

stability: implement audit findings remediation plan#38
tonyredondo merged 8 commits into
mainfrom
fix/audit-findings-hardening-2026-02

Conversation

@tonyredondo

Copy link
Copy Markdown
Member

Summary

  • Implement the validated audit remediation plan across runtime generation, CI/release policy, Python/Starlark tooling, and documentation, and track all 61 findings as closed with evidence in docs/audit/findings_validation_2026_02.md.
  • Extract uploader runtime implementations into standalone templates (.sh/.ps1/.bat), render them via expand_template, and enforce Windows PowerShell-only execution paths (no Git Bash dependency) for uploader/runtime and integration harness entrypoints.
  • Harden safety and reproducibility controls: hash-locked Python requirements, release workflow parity with CI quality lanes, .bazelversion parity checks, stricter template substitution validation, and Chainguard policy repo correction.

Test plan

  • python3 tools/dev/check_findings_ledger.py --require-done --require-evidence
  • python3 tools/dev/check_module_versions.py
  • python3 tools/dev/check_bazelversion_sync.py
  • python3 tools/dev/lint_uploader_templates.py --skip-shellcheck
  • python3 tools/tests/python/test_python_tools.py
  • ./bazelw test //tools/tests/core:tests //modules/go/tests:tests

Implement the validated remediation plan end-to-end: extract uploader runtimes into standalone templates, enforce a Windows PowerShell-only path, strengthen sync/uploader safety checks, expand release workflow parity, and close the findings ledger with evidence. This reduces drift between platforms and release lanes while making audit coverage and tooling validation deterministic.
@tonyredondo
tonyredondo requested a review from a team as a code owner February 20, 2026 09:20
Comment thread tools/tests/integration/run_mock_server_tests.ps1 Outdated
Fix post-review regressions by restoring uploader runtime template parity, exporting new test/tooling artifacts for Bazel visibility, and hardening bazelw version detection so enforcement works with non-standard version output formats. This brings full //... test execution and strict findings-ledger validation back to green.
Align uploader runtime fingerprint behavior with sync-side Starlark so API key parity checks stay deterministic across Bash and PowerShell. Remove Bash runtime Windows delegation and add regression tests that lock in PowerShell-only Windows behavior and cross-runtime fingerprint parity.
Comment thread tools/tests/python/test_python_tools.py Fixed
Format modified Starlark files to satisfy buildifier checks and remove the secret-like mock API key literal flagged during PR review. Replace regex-based Bash alphabet extraction in tests with deterministic parsing to avoid regex backtracking risk while preserving runtime parity validation.
Use separate stdout and stderr redirection files in the Windows integration harness so Start-Process works reliably on GitHub Windows runners. This resolves the bazel-tests windows job failure in PR #38.
Use PowerShell New-Item -Path for repository-rule directory creation so Windows fetches succeed on CI environments where -LiteralPath is not accepted for New-Item. Add a regression test that locks this command shape in the sync module.
Restore the Chainguard STS configuration to the tests repository identity and remove the audit source artifacts as requested. Add maintainer-focused documentation across changed runtime, sync, tooling, and test helpers so behavior and intent are easier to reason about during future maintenance.
Drop the audit findings ledger checker from CI/release workflows and remove the helper script now that docs/audit is no longer part of the repository. Update developer docs and exports to keep policy, tooling, and workflow behavior consistent.
@tonyredondo
tonyredondo merged commit 68b4f4f into main Feb 20, 2026
17 checks passed
@tonyredondo
tonyredondo deleted the fix/audit-findings-hardening-2026-02 branch February 20, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants