
Upstream software project
accessible-pygments
A collection of accessible pygments styles
About accessible-pygments
A collection of accessible pygments styles
This project links 4 native package records across 3 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
Project identity
- Project
- accessible-pygments
- Publisher
- Not authoritatively mapped
- Native package records
- 4
- Operating systems
- debian-13, opensuse-leap-16-0, opensuse-tumbleweed
- License expression
- BSD-3-Clause
- Metadata completeness
- 100/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Open source repository
Source-reported description
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
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.
Debian 13 (Trixie)
- python3-accessible-pygments0.0.5-2
Debian 13 (Trixie) / python / source accessible-pygments
Collection of accessible pygments styles
alltrixie
openSUSE Leap 16.0
- python313-accessible-pygments0.0.4-bp160.1.1
openSUSE Leap 16.0 / Unspecified / source python-accessible-pygments
A collection of accessible pygments styles
noarchleap-16.0
openSUSE Tumbleweed
- python313-accessible-pygments0.0.5-1.5
openSUSE Tumbleweed / Unspecified / source python-accessible-pygments
A collection of accessible pygments styles
noarchtumbleweed - python314-accessible-pygments0.0.5-1.5
openSUSE Tumbleweed / Unspecified / source python-accessible-pygments
A collection of accessible pygments styles
noarchtumbleweed
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.