Upstream software project

ghc-hackage-security

Haskell hackage-security library documentation

About ghc-hackage-security

Haskell hackage-security library documentation

This project links 18 native package records across 5 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

Fedora 43: 4 package records; Fedora 44: 4 package records; openSUSE Leap 15.6: 2 package records; openSUSE Leap 16.0: 4 package records; openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.ghc-hackage-security: recorded package coverageFedora 434 recordsFedora 444 recordsopenSUSE Leap 15.62 recordsopenSUSE Leap 16.04 recordsopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ghc-hackage-security
Publisher
Not authoritatively mapped
Native package records
18
Operating systems
fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
BSD-3-Clause
Source repository
Not reported

Source-reported description

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

The hackage security library provides both server and client utilities for securing the Hackage package server (<https://hackage.haskell.org/>). It is based on The Update Framework (<https://theupdateframework.com/>), a set of recommendations developed by security researchers at various universities in the US as well as developers on the Tor project (<https://www.torproject.org/>). The current implementation supports only index signing, thereby enabling untrusted mirrors. It does not yet provide facilities for author package signing. The library has two main entry points: "Hackage.Security.Client" is the main entry point for clients (the typical example being 'cabal'), and "Hackage.Security.Server" is the main entry point for servers (the typical example being 'hackage-server').

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 ghc-hackage-security

    43 (Fedora 43) (Unspecified): Hackage security library

    0.6.2.6-2.fc43: aarch64 x86_64

    Source: ghc-hackage-security

  2. Package ghc-hackage-security-devel

    43 (Fedora 43) (Unspecified): Haskell hackage-security library development files

    0.6.2.6-2.fc43: aarch64 x86_64

    Source: ghc-hackage-security

  3. Package ghc-hackage-security-doc

    43 (Fedora 43) (Unspecified): Haskell hackage-security library documentation

    0.6.2.6-2.fc43: noarch

    Source: ghc-hackage-security

  4. Package ghc-hackage-security-prof

    43 (Fedora 43) (Unspecified): Haskell hackage-security profiling library

    0.6.2.6-2.fc43: aarch64 x86_64

    Source: ghc-hackage-security

Fedora 44

  1. Package ghc-hackage-security

    44 (Fedora 44) (Unspecified): Hackage security library

    0.6.3.2-1.fc44: aarch64 x86_64

    Source: ghc-hackage-security

  2. Package ghc-hackage-security-devel

    44 (Fedora 44) (Unspecified): Haskell hackage-security library development files

    0.6.3.2-1.fc44: aarch64 x86_64

    Source: ghc-hackage-security

  3. Package ghc-hackage-security-doc

    44 (Fedora 44) (Unspecified): Haskell hackage-security library documentation

    0.6.3.2-1.fc44: noarch

    Source: ghc-hackage-security

  4. Package ghc-hackage-security-prof

    44 (Fedora 44) (Unspecified): Haskell hackage-security profiling library

    0.6.3.2-1.fc44: aarch64 x86_64

    Source: ghc-hackage-security

openSUSE Leap 15.6

  1. Package ghc-hackage-security

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Hackage security library

    0.6.2.0-bp156.3.4: aarch64 ppc64le s390x x86_64

    Source: ghc-hackage-security

  2. Package ghc-hackage-security-devel

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Haskell hackage-security library development files

    0.6.2.0-bp156.3.4: aarch64 ppc64le s390x x86_64

    Source: ghc-hackage-security

openSUSE Leap 16.0

  1. Package ghc-hackage-security

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Hackage security library

    0.6.2.6-bp160.1.12: aarch64 ppc64le x86_64

    Source: ghc-hackage-security

  2. Package ghc-hackage-security-devel

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Haskell hackage-security library development files

    0.6.2.6-bp160.1.12: aarch64 ppc64le x86_64

    Source: ghc-hackage-security

  3. Package ghc-hackage-security-doc

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Haskell hackage-security library documentation

    0.6.2.6-bp160.1.12: noarch

    Source: ghc-hackage-security

  4. Package ghc-hackage-security-prof

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Haskell hackage-security profiling library

    0.6.2.6-bp160.1.12: aarch64 ppc64le x86_64

    Source: ghc-hackage-security

openSUSE Tumbleweed

  1. Package ghc-hackage-security

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Hackage security library

    0.6.3.3-1.3: x86_64

    Source: ghc-hackage-security

  2. Package ghc-hackage-security-devel

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Haskell hackage-security library development files

    0.6.3.3-1.3: x86_64

    Source: ghc-hackage-security

  3. Package ghc-hackage-security-doc

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Haskell hackage-security library documentation

    0.6.3.3-1.3: noarch

    Source: ghc-hackage-security

  4. Package ghc-hackage-security-prof

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Haskell hackage-security profiling library

    0.6.3.3-1.3: x86_64

    Source: ghc-hackage-security

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.