Skip to content

docs: update case studies with v1.6.0 data, npm audit comparison, and content cleanup - #195

Merged
sonukapoor merged 3 commits into
mainfrom
docs/update-case-studies-v1.6.0
Apr 17, 2026
Merged

sonukapoor merged 3 commits into
mainfrom
docs/update-case-studies-v1.6.0

Conversation

@sonukapoor

@sonukapoor sonukapoor commented Apr 17, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Added new sections to both case studies: Summary, What this demonstrates, Comparison Note (npm audit head-to-head table), Before vs After, Fix Journey, Why this matters
  • Ran both tools against the same lockfiles to document the advisory-count vs package-count difference (55 vs 19 for Juice Shop, 36 vs 26 for NestJS)
  • Removed duplicate older sections that were fully covered by the new content
  • Kept unique technical detail: Project context (revision hash, scan command, .npmrc quirk), Remaining risk (specific package lists)
  • Added > Tested with CVE Lite CLI v1.6.0 version marker to both files

Test plan

  • Read both case studies end-to-end for flow and accuracy
  • Verify all numbers in tables match the stated tool versions
  • Confirm no conflict markers or leftover duplicate paragraphs

Closes #187

- Add Summary, What this demonstrates, Comparison Note, Before vs After,
  Fix Journey, and Why this matters sections to both case studies
- Include side-by-side npm audit vs CVE Lite CLI v1.6.0 data tables
- Explain why CVE Lite's lower finding count is deduplication, not
  reduced coverage — advisory IDs are still surfaced in verbose output
- Add version marker: Tested with CVE Lite CLI v1.6.0
- Preserve all existing commands, outputs, and remediation walkthrough
…t comparison

Both case studies now open with a tighter set of new sections (Summary,
What this demonstrates, Comparison Note with npm audit table, Before vs
After, Fix Journey, Why this matters) and retain only the unique
technical detail from the older content (Project context, Remaining risk
package lists).

Removed: Outcome at a glance, Executive summary, Why this was not a zero
CVEs exercise, Remediation journey, Copy-and-run output, Top-priority
findings, What developers usually get wrong, Key takeaways, and the old
Why this case study matters — all superseded by the new sections.

Closes #187
@sonukapoor
sonukapoor merged commit 94f2ae5 into main Apr 17, 2026
3 checks passed
@sonukapoor
sonukapoor deleted the docs/update-case-studies-v1.6.0 branch April 17, 2026 03:43
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.

docs: update case studies with v1.6.0 scan data, npm audit comparison, and content cleanup

1 participant