CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

devel/rubygem-event_stream_parser 1.0.0

Spec-compliant event stream parser

0
unaddressed
0
VuXML only
0
fixed
0
open problem reports

Port info

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 1.0.0
Upstream
up to date
Last update
to 1.0.0 · ad1c20fa7a
Quarterly
2026Q4: 1.0.0
WWW
https://github.com/Shopify/event_stream_parser
Links
cgit · VuXML

Install

Package
# pkg install rubygem-event_stream_parser
installs 1.0.0 from latest; from quarterly (2026Q4) 1.0.0
Port
# cd /usr/ports/devel/rubygem-event_stream_parser && make install clean
Size
5.8 KiB download · 13 KiB installed
Depends on
devel/ruby-gems 4.0.21, lang/ruby34 3.4.9_2,1
License
MIT

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 161.0.01.0.0–
FreeBSD 151.0.01.0.0–
FreeBSD 141.0.01.0.01.0.0

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 151.0.01.0.0–
FreeBSD 141.0.01.0.01.0.0

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 1.0.0.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (2)

Po-Chuan Hsieh (sunpoet) · 1.0.0
devel/rubygem-event_stream_parser: Update to 1.0.0

Changes:	https://github.com/Shopify/event_stream_parser/blob/main/CHANGELOG.md
ad1c20fa7a
Po-Chuan Hsieh (sunpoet) · 0.3.0
devel/rubygem-event_stream_parser: Add rubygem-event_stream_parser 0.3.0

event_stream_parser is a lightweight, fully spec-compliant parser for the event
stream format.

It only deals with the parsing of events and not any of the client/transport
aspects. This is not a Server-sent Events (SSE) client.

Under the hood, it's a stateful parser that receives chunks (that are received
from an HTTP client, for example) and emits events as it parses them. But it
remembers the last event id and reconnection time and keeps emitting them as
long as they are not overwritten by new ones.

BOM stripping is left as a responsibility of the chunk provider.
34997bf1ce