kodebeat / papers / security
Knowing what your dependencies are doing
Sbom-diff and depwatch.
Dependency risk is two questions, and answering one well is why teams believe they have answered both. sbom-diff explains a lockfile bump in plain language, ranked by consequence; depwatch plots how far behind a dependency is against whether anyone is still there to catch up with. Neither is a vulnerability scanner, and both are designed to sit beside one.
What is in it
- The problem — what goes unanswered without it, and who notices first.
- Why the obvious alternative falls short — stated plainly, including where it is the better choice.
- How it works — the method, not a feature list.
- Concrete use cases — with console output quoted from the repository, never reconstructed.
- The methodology behind any number it emits — every term shown, so the figure survives a question.
- What it deliberately does not do — the section most papers leave out.
Part of the Security & supply chain theme.
Get the PDF
One email with the download link, and this paper already selected. No follow-up sequence.