Home / Articles / Chainguard, mapped / Versions / v1.3.0
Chainguard, mapped: what changed in v1.3.0
From v1.2.0 (2026-10-19, d303ce0f1) to v1.3.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 61 unchanged. About 0 words added and 67 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot cn-map.webp | images/ | Chainguard, mapped.mapped Fromfrom the operating system to agents: what it builds, the public data a third party can read today,data, and where an opena policy and an encrypted vault could add the context that decides whether an image can ship.help. | comparison
29 unchanged paragraphs, under In short {#in-short}, Why Chainguard {#why}, The company {#company}…
!shot cn-context.webp | images/ | How far up the stack the context goes.goes: from Chainguard's package data describes packages and the components inside them; the decision whether an image can ship today is aboutto the application above: is the vulnerable code reachable from what is exposed? A context layer from the user story to the code would sort each finding into must fix, ship nowabove, with athree reason, and ship now and watch.outcomes. | architecture
30 unchanged paragraphs, under The context layer {#context}, Where we plug in {#plug-in}, What this does not claim {#limits}…