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

textproc/uni-algo 1.2.0

Unicode Algorithms Implementation for C/C++

Port info

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 1.2.0
Upstream
up to date
Last update
to 1.2.0 · 22fcd914de
Quarterly
2026Q4: 1.2.0
WWW
https://github.com/uni-algo/uni-algo
Links
cgit · VuXML

Install

Package
# pkg install uni-algo
installs 1.2.0 from latest; from quarterly (2026Q4) 1.2.0
Port
# cd /usr/ports/textproc/uni-algo && make install clean
Size
294 KiB download · 2.6 MiB installed
Depends on
nothing
License
MIT or PD

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 161.2.01.2.0–
FreeBSD 151.2.01.2.0–
FreeBSD 141.2.01.2.01.2.0

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 151.2.01.2.0–
FreeBSD 141.2.01.2.01.2.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.2.0.

Fixed (0)

No VuXML entries for this package.

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

None.

Commits (1)

Po-Chuan Hsieh (sunpoet) · 1.2.0
textproc/uni-algo: Add uni-algo 1.2.0

There are plenty of Unicode libraries for C/C++ out there that implement random
Unicode algorithms, but many of them don't handle ill-formed UTF sequences at
all.  In the best-case scenario, you'll get an exception/error; in the
worst-case, undefined behavior. The biggest problem is that in 99% cases
everything will be fine. This is inappropriate for security reasons.  This
library handles such problems (there are not only ill-formed sequences actually)
properly and always according to The Unicode Standard.

In C/C++, unlike some other programming languages, there is no safe type for
UTF-8/UTF-16 that guarantees that the data will be well-formed; this makes the
problem even worse. The library doesn't introduce such a type either because the
library doesn't work with types/strings/files/streams, it works with the data
inside them and makes it safe when it's needed.

Check this article if you want more information about ill-formed sequences:
https://hsivonen.fi/broken-utf-8

It is a bit outdated because ICU (International Components for Unicode) now uses
W3C conformant implementation too, but the information in the article is very
useful.

This library does use W3C conformant implementation too.
22fcd914de