Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

13 changes behind one line · newest first

SinceClear the filter
ChangedSourceRows

One change, in full: Package added to advisory: scriban.signed named as affected in nuget. The same change in 13 advisories. Back to the ledger

Counted changes, newest first, one line per change to a GHSA advisory, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindAdvisory, Which advisory was edited, by its GHSA id.Package, The package the advisory names, and the registry it comes from.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
2026-07-06published 2026-06-26Package added to advisoryGHSA-6q7j-xr26-3h2cmoderatenot named as affected when the advisory was published, now names scriban.signedTime to revision 10 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-xw6w-9jjh-p9crmoderatenot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-m2p3-hwv5-xpqwmoderatenot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-xcx6-vp38-8hr5highnot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-v66j-x4hw-fv9ghighnot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-5wr9-m6jw-xx44criticalnot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-x6m9-38vm-2xhfhighnot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-p6q4-fgr8-vx4phighnot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days
2026-07-06published 2026-03-19Package added to advisoryGHSA-5rpf-x9jg-8j5pmoderatenot named as affected when the advisory was published, now names scriban.signedTime to revision 109 days
2026-07-06published 2026-03-19Package added to advisoryGHSA-grr9-747v-xvcphighnot named as affected when the advisory was published, now names scriban.signedTime to revision 109 days
2026-07-06published 2026-03-19Package added to advisoryGHSA-wgh7-7m3c-fx25highnot named as affected when the advisory was published, now names scriban.signedTime to revision 109 days
2026-07-06published 2026-06-26Package added to advisoryGHSA-q6rr-fm2g-g5x8moderatenot named as affected when the advisory was published, now names scriban.signedTime to revision 10 days
2026-07-06published 2026-03-24Package added to advisoryGHSA-c875-h985-hvrchighnot named as affected when the advisory was published, now names scriban.signedTime to revision 104 days

Counted in advisories, never added to the CVE and KEV figures. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →