Upstream software project

golang-github-rasky-xdr

Implements the XDR standard as specified in RFC 4506 in pure Go

About golang-github-rasky-xdr

Implements the XDR standard as specified in RFC 4506 in pure Go

This project links 1 native package record across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

golang-github-rasky-xdr repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records. Catalog coverage diagram, not an application screenshot.golang-github-rasky-xdr: recorded package coverageFedora 431 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
golang-github-rasky-xdr
Publisher
Not authoritatively mapped
Native package records
1
Operating systems
fedora-43
License expression
ISC
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Implements the XDR standard as specified in RFC 4506 in pure Go. This package contains the source code needed for building packages that reference the following Go import paths: – github.com/rasky/go-xdr

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package golang-github-rasky-xdr-devel

    43 (Fedora 43) (Unspecified): Implements the XDR standard as specified in RFC 4506 in pure Go

    0-0.15.20190702git1a41d1a.fc43: noarch

    Source: golang-github-rasky-xdr

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.