Upstream software project

golang-github-dreamacro-shadowsocks2

Experimental Shadowsocks in Go

About golang-github-dreamacro-shadowsocks2

Experimental Shadowsocks in Go

This project links 4 native package records across 2 recorded operating-system releases. 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-dreamacro-shadowsocks2 repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.golang-github-dreamacro-shadowsocks2: recorded package coverageFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
golang-github-dreamacro-shadowsocks2
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
fedora-43, fedora-44
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

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

Experimental Shadowsocks in Go. Stable fork at https://github.com/shadowsocks/go-shadowsocks2. This package contains the source code needed for building packages that reference the following Go import paths: – github.com/Dreamacro/go-shadowsocks2

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. Source: golang-github-dreamacro-shadowsocks2

  2. Source: golang-github-dreamacro-shadowsocks2

Fedora 44

  1. Source: golang-github-dreamacro-shadowsocks2

  2. Source: golang-github-dreamacro-shadowsocks2

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.