/ feed22 advisory · 26 mixed · 326 release-note streams
Checked · Target interval 120 minutes
go-redis: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
Checked · Target interval 120 minutes
fasthttp: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
Checked · Target interval 120 minutes
quic-go: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
1 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
Caddy: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
2 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
Hyper: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
Checked · Target interval 120 minutes
Tonic: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
7 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
Axum: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
5 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
Tokio: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
4 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
Actix Web: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
1 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
Reqwest: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
Checked · Target interval 120 minutes
Rustls: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
3 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
WebPKI: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
1 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
RustCrypto hashes: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
3 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
Serde: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
5 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
serde_json: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
7 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
zip crate: Go and Rust HTTP, TLS, archive and serialization components are common foundations of network-facing services.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
1 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
OpenSSL: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
Checked · Target interval 120 minutes
wolfSSL: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
6 checked entries were not usable (Feed item lacks substantive release notes; Empty or oversized document; requires a dedicated adapter)
Checked · Target interval 120 minutes
Mbed TLS: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
5 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
libsodium: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
7 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
nghttp2: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
Checked · Target interval 120 minutes
ngtcp2: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
Checked · Target interval 120 minutes
Expat: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
3 checked entries were not usable (Feed item lacks substantive release notes)
Checked · Target interval 120 minutes
zlib: Native cryptographic, network, image, XML and archive libraries are high-impact memory-safety and parsing boundaries.
Release notes are not a dedicated advisory channel. Only security information present in the notes can be extracted; external changelogs and repository security advisories are not automatically followed.
6 checked entries were not usable (Feed item lacks substantive release notes)
Structured advisory databases are configured by default; vendor feeds are opt-in. Catalog entries do not establish live uptime or complete coverage. Vendor checks verify retrieval and parsing, not extraction accuracy.