RustSec repository updates advisory IDs and metadata in February sync

RustSec's advisory-db repository on GitHub recorded synchronization commits between 2026-02-13 and 2026-02-14 that added advisory IDs and synchronized metadata for the February batch of advisories. The change set was logged in the advisory-db repo and is visible as a commit on the platform, providing a concrete update point for the database that many Rust projects pull for vulnerability data.

The February batch of advisories saw metadata synchronization across affected entries, with advisory IDs added to records that previously lacked them. Those edits were part of the synchronization activity over the two-day window, and they specifically targeted entries included in the February rollout rather than piecemeal or single-entry fixes.

Included in the synchronization were polymarket-related removals; the February sync recorded removals tied to polymarket-related entries alongside the metadata and ID updates. The repository activity therefore combined additive changes - advisory IDs and metadata harmonization - with selective removals associated with polymarket-related items.

A visible commit on GitHub captures the February-sync snapshot, enabling maintainers and auditors to inspect the exact diffs for the advisory-db repository. Because the repository changes were consolidated between 2026-02-13 and 2026-02-14, the commit history supplies a clear boundary for downstream consumers to compare local copies against the authoritative advisory-db state published in that window.

If you track advisory-db updates for audits or tooling, confirm which commit you received from the Feb 13-14 sync and whether the polymarket-related removals appeared in your local copy; did your repository pull include the visible commit from the February batch?