Skip to content

ci(zizmor): document-ignore intentional adhoc-package installs - #227

Merged
kyle-sexton merged 1 commit into
mainfrom
chore/zizmor-burn-down-notes
Jul 21, 2026
Merged

ci(zizmor): document-ignore intentional adhoc-package installs#227
kyle-sexton merged 1 commit into
mainfrom
chore/zizmor-burn-down-notes

Conversation

@kyle-sexton

Copy link
Copy Markdown
Contributor

Burn down the note-level zizmor findings that were annotating every PR (all below the fail-on-severity: high gate added in #225).

  • ci.yml:404,589 (adhoc-packages): the two exact-pinned npm install -g tsc/biome steps install toolchains on PATH so the contract tests can drive the tools directly — deliberate and documented. Add inline # zizmor: ignore[adhoc-packages] <rationale>.
  • publish-packages.yml:83 (use-trusted-publishing): a real security recommendation (drop the long-lived token for OIDC). Left visible and tracked in security(publish-packages): adopt npm OIDC trusted publishing #226 — the proper fix needs npm-org trusted-publisher config.

After this, zizmor --persona=regular reports only the single tracked note.

Related

No related issue: annotation-noise burn-down following the gate rollout (#225, ci-workflows#183). Deferred proper fix tracked in #226.

The two `npm install -g` steps (exact-pinned tsc/biome) install toolchains on
PATH so the tsconfig/biome contract tests can drive the tools directly — a
deliberate, documented pattern, not a supply-chain gap. Add inline
`# zizmor: ignore[adhoc-packages] <rationale>` so the annotations stop
recurring on every PR.

The remaining `use-trusted-publishing` note (publish-packages.yml) is a real
recommendation left visible and tracked in #226 (OIDC adoption needs
registry-side config); it is below the `fail-on-severity: high` gate.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@claude

claude Bot commented Jul 21, 2026

Copy link
Copy Markdown

Claude finished @kyle-sexton's task in 59s —— View job


Review

  • Read changed files and PR context
  • Check REVIEW.md criteria
  • Analyze annotation correctness and security posture
  • Post review

Summary: Annotation-only noise-reduction PR. No logic changes. All blocking criteria from REVIEW.md are not applicable here (no auth paths, no secrets, no injection surfaces, no multi-tenancy, no atomicity concerns). The two suppressions are correct and well-justified.

Line 404 — TypeScript install (permalink)

The adhoc-packages finding is suppressed here because the install is:

  • Exact-version-pinned via typescript@$TYPESCRIPT_VERSION (resolved from matrix.typescript)
  • Required on PATH for the tsconfig contract test to drive tsc directly

The suppression is accurate and the rationale in the comment maps to the real behavior.

Line 589 — Biome + TypeScript install (permalink)

Same pattern: both @biomejs/biome@${BIOME_VERSION} and typescript@${TYPESCRIPT_VERSION} are exact-version-pinned. The comment correctly names both contract tests that depend on this toolchain.

use-trusted-publishing decision

Leaving the publish-packages.yml finding visible and tracking it in #226 is the right call — OIDC trusted publishing is a real recommendation, not annotation noise, and deferring it preserves that signal without creating a false silence.

zizmor ignore syntax

# zizmor: ignore[adhoc-packages] is the correct inline suppression syntax. Both annotations place the comment at the end of the run: line, which is where zizmor expects it for shell-command suppressions.

No findings. Looks good to merge.

@kyle-sexton
kyle-sexton merged commit 9f48d76 into main Jul 21, 2026
42 checks passed
@kyle-sexton
kyle-sexton deleted the chore/zizmor-burn-down-notes branch July 21, 2026 01:32
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.

1 participant