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

devel/rubygem-opentelemetry-registry 0.6.3

Registry for the OpenTelemetry Instrumentation libraries

Port info

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 0.6.3
Upstream
up to date
Last update
to 0.6.3 · f914278a58
Quarterly
2026Q4: 0.6.3
WWW
https://opentelemetry.io/
Links
cgit · VuXML

Install

Package
# pkg install rubygem-opentelemetry-registry
installs 0.6.3 from latest; from quarterly (2026Q4) 0.6.3
Port
# cd /usr/ports/devel/rubygem-opentelemetry-registry && make install clean
Size
8.5 KiB download · 32 KiB installed
Depends on
devel/ruby-gems 4.0.21, devel/rubygem-opentelemetry-api 1.11.1, lang/ruby34 3.4.9_2,1
License
APACHE20

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 160.6.30.6.3–
FreeBSD 150.6.30.6.3–
FreeBSD 140.6.30.6.30.6.3

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 150.6.30.6.3–
FreeBSD 140.6.30.6.30.6.3

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 0.6.3.

Fixed (0)

No VuXML entries for this package.

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

None.

Commits (8)

Po-Chuan Hsieh (sunpoet) · 0.6.3
devel/rubygem-opentelemetry-registry: Update to 0.6.3

Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
f914278a58
Po-Chuan Hsieh (sunpoet) · 0.6.1
devel/rubygem-opentelemetry-registry: Update to 0.6.1

Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
133a53f72f
Po-Chuan Hsieh (sunpoet) · 0.6.0
devel/rubygem-opentelemetry-registry: Update to 0.6.0

Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
f444c5750d
Po-Chuan Hsieh (sunpoet) · 0.5.0
devel/rubygem-opentelemetry-registry: Update to 0.5.0

Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
071e75b1c7
Po-Chuan Hsieh (sunpoet) · 0.4.0
devel/rubygem-opentelemetry-registry: Update WWW
bf0e6b9c5b
Po-Chuan Hsieh (sunpoet) · 0.4.0
devel/rubygem-opentelemetry-registry: Update to 0.4.0

Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
da41f55698
Po-Chuan Hsieh (sunpoet) · 0.3.1
devel/rubygem-opentelemetry-registry: Update to 0.3.1

Changes:	https://github.com/open-telemetry/opentelemetry-ruby/releases
		https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md
a4c6176889
Po-Chuan Hsieh (sunpoet) · 0.3.0
devel/rubygem-opentelemetry-registry: Add rubygem-opentelemetry-registry 0.3.0

The instrumentation Registry contains information about available
instrumentation, facilitates discovery, installation, and configuration.

The Registry allows for instrumentation to avoid depending directly on a
specific SDK implementation.

The SDK depends on the Registry, the instrumentation Base class depends on the
Registry, and auto instrumentation libraries extend the instrumentation Base
class.

The motivation for decoupling the Registry (and by extension the
instrumentation) from a specific SDK implementation means that anyone can
implement their own OpenTelemetry API compatible SDK, and they could continue to
use community made instrumentation.
53adcca119