Commit baf0a41
authored
docs(ci): record why the escalation job's setup-node scan finding was dismissed (#10153)
A scanner flagged actions/setup-node in the escalate-persistent-failure job
(#10146) as a filesystem-read risk, citing __tests__/authutil.test.ts.
That is a test fixture inside setup-node's own repository, not runtime
behaviour, and the feature it exercises -- writing an auth token into .npmrc --
only engages when `registry-url` is supplied. It is supplied in the five
publish-*.yml workflows and deliberately not here, so the path is inert in this
job. The pin is also the same SHA as all 32 other setup-node uses in the repo,
including build-boot in this same file, so the job introduced no dependency
that was not already present.
No behaviour change -- the finding was reviewed and dismissed, and the reason is
recorded here so the next scan does not cost another investigation. The note
names the condition that would invalidate it (this step gaining registry-url)
rather than dismissing the rule outright.1 parent 453e7af commit baf0a41
1 file changed
Lines changed: 9 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
195 | 195 | | |
196 | 196 | | |
197 | 197 | | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
198 | 207 | | |
199 | 208 | | |
200 | 209 | | |
| |||
0 commit comments