ci(chapter-21): run audit and security lint checks in CI
Chapter: 21 - Security checks in the merge path. Plain-English map: Add npm audit and ESLint security scanning to the CI pipeline. Why it matters: Dependency risk and unsafe patterns should show up during pull request review, not after deployment. Principle: Security automation belongs where code is merged. Precedent borrowed: The fork report's dominant security PR cluster and common CI hardening practice. Upstream base: willchen96/mike@d39f580. Original local commit: 8cda4ca.
| Repository | amal66/mike |
|---|---|
| Author | Amal <mamalanand3@gmail.com> |
| Authored | |
| Parents | fd362463 |
| Stats | 1 file changed , +10 |
| Part of | Add supply-chain audit ratchet and Dependabot |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-bb249e0f.md
from inside the repo you want the change in.