Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
The first line of the daily EPSS file names the model version and score date. Cite both, plus the row count, so an EPSS figure can be reproduced.
Pick the dataset by the question: KEV for known exploitation, EPSS for likelihood, OSV for package versions, NVD for CVE records. Here is a decision table.
AI assistants answer platform questions fast but can be dated or wrong. Six checks to verify claims on capabilities, standards, and fit before you act.
Flat monthly AI plans still carry usage limits. Here is what a five-hour session limit and a weekly limit are, what counts, and what your options are.
KEV entries can list zero to four CWEs, so counting by entry or by label gives different shares. Here is how to pick a denominator and state it clearly.
Six common claims about IAST and RASP checked against OWASP and Oracle documentation: zero false positives, no code changes, set and forget, and more.
To cite a KEV figure, record catalogVersion, dateReleased and count from the JSON feed, plus your fetch date and a file hash so readers can reproduce it.
Fix errors in the open: change the number, add a dated corrections note, and keep a log of old value, new value and cause so citing sites can update.
A smooth AI agent demo hides defaults, limits and failure modes. Questions to ask about scheduled tasks, files, desktop apps and sandboxes before you sign.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.
