mradermacher

Hypa-Gemma4-E2B-v1-i1-GGUF

Translation
What we checked

File: check availability in Files.

Memory: Fit unknown. File size needed to check fit.

Last recorded run: none for this selected file.

License BFiles CRuns F

Recorded checks do not guarantee safety or performance on your computer.

See file checks and sources
Translate textGGUFLicense label: apache-2.0

About this artifact

External Hugging Face catalog record for mradermacher/Hypa-Gemma4-E2B-v1-i1-GGUF. Task: translation. Library: transformers. Languages: en, fr, es, ha, ig, yo, efi, ibb. Datasets referenced by card metadata: hypaai/Hypa-Text-10k. Base model: hypaai/Hypa-Gemma4-E2B-v1. Popularity signal at import: 548 downloads and 1 likes.

Hosted file inventory

Hosted files
1 of 18
Reviewed peer-assisted fallbacks
0
Trust bundle
Trust-bundle JSON
Review summary
Review-summary JSON
Distribution
Reviewed peer-fallback JSON

    Run status

    Detailed evidence for the selected file set

    This detail applies to the selected file set, not every file in the repository.

    Executable state
    complete-bytes
    Evidence timestamp
    2026-09-22T23:00:11.968Z
    Selected representation
    rep-c47f1fef7ac9ff52eff9561335c88586ad38ea3fa107f6a01f953a71942cf2b9
    Complete bytes
    yes
    Complete kit
    no
    Byte-integrity check
    not established. The hosted bytes are not yet matched to a signed upstream manifest
    Run ready
    not established
    Files
    View file metadata

    Bay Run

    Hosted file

    Bay Run does not serve this exact artifact, and Hugging Bay will not invent a run contract for it. Hugging Bay hosts the file below: download it and check the sha256 before running it locally.

    Hypa-Gemma4-E2B-v1.i1-Q4_K_M.gguf · 3.2 GB · sha256 d433f99df4ddea0ac40cac72a30139632f4e562bac44139c418cb14ba63e1fd3

    Guard before generate

    Add Bay Run's provider-neutral coprocessor to your own generation pipeline. It checks decision.action before your generator runs.

    npm install @huggingbay/coprocessor · Install @huggingbay/coprocessor

    This handoff wraps your caller-owned generator. It does not run this catalog artifact, make it a Bay Run Pin, or change its serving or verification state.

    Request a complete representation

    • License: pass - apache-2.0
    • Provenance: pass - mradermacher/Hypa-Gemma4-E2B-v1-i1-GGUF
    • Scan: pass - passed
    • Hosted files: warn - external metadata only
    • Byte manifest integrity: warn - not final yet

    Machine-readable card

    Open interactive artifact page

    Additional model information
    Quick answer: compatibility and sources

    Can I run Hypa-Gemma4-E2B-v1-i1-GGUF on my computer?

    It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

    Hypa-Gemma4-E2B-v1-i1-GGUF is an open-weights language model for translation. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.

    As of the recorded file availability check on .

    Recorded SHA-256 for Hypa-Gemma4-E2B-v1.i1-Q4_K_M.gguf: d433f99df4ddea0ac40cac72a30139632f4e562bac44139c418cb14ba63e1fd3. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.

    Page text updated .

    Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .

    Key facts

    Catalog record
    Summarizes upstream metadata; it is not itself a download or run receipt.
    File evidence
    Lists exact filenames, availability and any recorded SHA-256 for individual files.
    Run evidence
    Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
    Checksum scope
    SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.

    Evidence you can inspect (plain text)

    • This page’s quick answer names the file record for hf-model-mradermacher-hypa-gemma4-e2b-v1-i1-gguf.
    • Open /artifact/hf-model-mradermacher-hypa-gemma4-e2b-v1-i1-gguf/files for exact filenames, availability and any recorded SHA-256 for this model.
    • Open /evidence/artifacts/hf-model-mradermacher-hypa-gemma4-e2b-v1-i1-gguf for run-readiness evidence tied to that record; absent receipts stay unmeasured.
    • Open /api/artifacts/hf-model-mradermacher-hypa-gemma4-e2b-v1-i1-gguf/card.md for machine-readable source facts (not a runtime test).
    • A matching checksum on this page fingerprints only the named bytes shown in file evidence.

    Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.

    Which date applies to which fact

    • File availability check:
    • Committed page-copy sources:
    • Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
    • Run receipts: Only on /evidence pages when recorded; otherwise unmeasured

    Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.