Repository navigation
Description
Prepare a bounded security follow-up for the repository state observed on 2026-10-22. Refresh the affected source and settings before editing; this snapshot is not evidence of compromise.
Actions permission baseline:
- Settings → Actions → General → Workflow permissions was set to the read/write default. Propose the read-only default and audit explicit workflow/job
permissions:so only jobs requiring publishing or another write operation receive their specific scopes. This is a repository DEFAULT finding; it does not establish that every workflow currently has write permissions. Preserve required release and reusable-workflow behavior.
Mutable Actions references (repository-relative paths; repeated references grouped):
.github/workflows/publish.yml[default_branch]:actions/checkout@v4,actions/setup-node@v4,actions/setup-python@v5,pypa/gh-action-pypi-publish@release/v1.
Resolve each external action/reusable workflow to a verified full commit SHA; use an immutable image digest for Docker references. Keep version annotations and a reviewed update mechanism. Mutable tags are P2 supply-chain hardening findings, not evidence of malicious code. Local checkout observations may differ from the default branch.
Acceptance: produce a reviewed, minimal source/settings proposal with before/after evidence, scoped checks, retained uncertainty, and an explicit rollback. Repository settings changes and any live deployment, restart, credential action or external publication require separate owner authorization. An unsafe previous trust configuration must not be restored as an automatic rollback; prefer a documented fail-closed stop if needed.
Implementation brief and completion evidence
Reconcile these dated audit observations with current HEAD, deployed artifact identity and official advisories before editing. Read repository instructions, preserve unrelated work, and prepare focused fixes in an isolated worktree using the fleet worktree convention. Follow each checklist above; an advisory match, broad default or missing log does not establish exploitation. No blanket dependency upgrades. Never execute exploit payloads, inspect production data unnecessarily, or expose credentials in tests, logs, issues or PRs.
Use the smallest compatible change, inspect lockfile/provenance changes and run meaningful targeted checks followed by required broader verification. Test privileged paths with synthetic data in disposable environments. Document before/after behavior, exact source/artifact identity, residual risk and rollout/rollback requirements. A source fix is not proof that the running deployment is repaired.
Live deployment/restarts, firewall or security-policy changes, disruptive upgrades, credential revocation affecting workloads, destructive cleanup and merges require explicit owner approval. Do all safe source preparation and testing first. Never restore an unsafe authentication bypass as rollback. Close only completed scope; retain separate tracking for pending runtime rollout, ownership/access gaps or owner decisions.
Detailed confidential evidence is in the owner-private per-repository audit packet. Do not attach or publish it here. The checklist above is the portable implementation brief.
Activity