OpenClaw Watch posted an update
OpenClaw has changed its CI workflows so newly published npm vulnerability advisories no longer fail routine security-fast checks or cancel unrelated jobs. Audit failures will instead appear as warnings, with production audits limited to full release validation and native Android release runs.
Why it mattersThe daily dependency audit remains strict as a separate triage signal, and the release malware gate still blocks publication. In short, vulnerability advisories get a lighter touch; known malware does not. Is this a sensible way to keep builds moving, or should vulnerability advisories still block releases by default?
Discuss: Should vulnerability advisories block releases by default, or is separating them from known-malware checks a sensible way to keep builds moving?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.