Linux workstation

Debian 13 (Trixie) native package

openjdk-25-jvmci-jdk

用于构建 graalvm 的启用 JVMCI 的 SDK

Packages / Debian 13 (Trixie) / java / openjdk-25-jvmci-jdk

[Source: openjdk-25]

Package: openjdk-25-jvmci-jdk

[Project overview: openjdk-21]

Maintainers:

OpenJDK Team

External Resources:

Homepage: [openjdk.java.net]

Similar packages:

用于构建 graalvm 的启用 JVMCI 的 SDK

No published records match this suite and architecture filter.

Package-file coverage (not observed)

The active import did not include the repository's package-file index (Debian Contents for this cohort). This is missing coverage, not an observation that the package contains or installs zero files.

No package-associated file paths were observed for the displayed build metadata.

Use this package

OpenFactory can boot this operating system in a browser VM, or start a build that includes the native package name from this record.

Try Debian 13 (Trixie) in the browserBuild an image that includes openjdk-25-jvmci-jdk

Versions, suites, and repositories

Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.

No published records match this suite and architecture filter.

Checksums and observation dates

For an APT source, signature verification authenticates the repository metadata chain and the Packages index containing this source-reported artifact digest. It does not certify package safety.

Catalog record completeness

The completeness score measures metadata coverage, not software quality, security, compatibility, or suitability.

Summary and description
25/25
Artifact path and source digest
25/25
Dependency metadata
15/15
Package-file index
0/15
Homepage
5/5
License text
0/5
Source package or maintainer
10/10

Recorded total: 80/100

Field source: Debian Security revision trixie-security-main-amd64:5cf72f9c534b27dd9fb350b7d4c31b05a82dea2abcfed19a08097bf8d7e8f847. The cross-OS mapping is catalog-derived from the source-reported homepage; it does not establish authorship or publisher identity

Sources and provenance

Field-source links above resolve here. Each source entry names the metadata publisher, trust tier, exact snapshot revision, signature result, and observation time; catalog-derived mappings are labeled separately.

  • Debian SecurityOct 7, 2026

    Authoritative source; repository metadata signature verified, revision trixie-security-main-amd64:5cf72f9c534b27dd9fb350b7d4c31b05a82dea2abcfed19a08097bf8d7e8f847

    Signature verification covers the configured repository metadata chain. It does not certify that the package is safe or suitable.

    Repository-signature verification record
    Signed-object SHA-256
    4e3d5b0b8cee991cb99a0a49d423cfc67c218aa0f8afa4589d6a1c88e1bf5bf7
    Signer fingerprint
    B0CAB9266E8C3929798B3EEEBDE6D2B9216EC7A8
    Keyring revision
    debian-archive-keyring.gpg
    SHA-256 506b815cbb32d9b6066b4a2aa524071e071761e7e7f68c3ac74f3061ba852017
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Oct 9, 2026
    Signed Release → package-index hash linkage

    Path: main/binary-amd64/Packages.xz
    Expected SHA-256: 5cf72f9c534b27dd9fb350b7d4c31b05a82dea2abcfed19a08097bf8d7e8f847
    Observed SHA-256: 5cf72f9c534b27dd9fb350b7d4c31b05a82dea2abcfed19a08097bf8d7e8f847
    Result: match verified