qodana.yml runs qodana-js (Ultimate, QODANA_TOKEN) on pushes to main, pull
requests, a weekly schedule and by hand, in two jobs (docs/12 §2.7):
- `scan` installs the dev dependencies with scripts off — qodana-js resolves
types through them — and holds only a read-only GITHUB_TOKEN; PR comments
and annotations are off, the SARIF report is kept as an artifact;
- `publish` installs nothing and uploads that SARIF to code scanning
(category qodana), so the findings sit beside CodeQL's.
The action is pinned to the commit of v2026.2.2 (the newest tag is younger
than the 7-day cooldown). Sharing a runner with dependency code is recorded
as an exception to the Sonar rule: the token can only upload reports.
triage.yml, from review of the first draft:
- comment and close first, label last — the label is what a re-run reads as
done, so it must not exist before the work;
- an `enhancement` issue with no answer to the form is closed only when the
owner added the label; otherwise it goes to needs-triage;
- checkout and setup-node pinned to commits, no cache: this workflow runs
them with a write token on events anyone can trigger.
README gains the Qodana badge.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>