
Upstream software project
eclipse-egit
Eclipse JGit
About eclipse-egit
Eclipse JGit
This project links 6 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
Project identity
- Project
- eclipse-egit
- Publisher
- Not authoritatively mapped
- Native package records
- 6
- Operating systems
- opensuse-leap-15-6, opensuse-tumbleweed
- License expression
- BSD-3-Clause
- Metadata completeness
- 100/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Not reported
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.
openSUSE Leap 15.6
- eclipse-egit5.11.0-150200.3.6.3
openSUSE Leap 15.6 / Development/Libraries/Java / source eclipse-egit
Eclipse Git Integration
noarchleap-15.6 - eclipse-jgit5.11.0-150200.3.20.1
openSUSE Leap 15.6 / Development/Libraries/Java / source eclipse-jgit
Eclipse JGit
noarchleap-15.6 - jgit5.11.0-150200.5.3.3
openSUSE Leap 15.6 / Development/Libraries/Java / source jgit
Eclipse JGit
noarchleap-15.6 - jgit-javadoc5.11.0-150200.5.3.3
openSUSE Leap 15.6 / Documentation/HTML / source jgit
API documentation for jgit
noarchleap-15.6
openSUSE Tumbleweed
- jgit5.11.0-2.4
openSUSE Tumbleweed / Development/Libraries/Java / source jgit
Eclipse JGit
noarchtumbleweed - jgit-javadoc5.11.0-2.4
openSUSE Tumbleweed / Documentation/HTML / source jgit
API documentation for jgit
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.