Skip to content

fix(catalog): published catalog ships stale license labels for 14 models #7

Open

Description

@coygeek

Summary

The published catalog still gives 14 models license labels that transcribe.cpp has already corrected. Parakeet Unified English is labeled cc-by-4.0 instead of other (NVIDIA Open Model License), Whisper Large v3 Turbo is labeled apache-2.0 instead of mit, and 12 Moonshine language variants are labeled mit instead of other (Moonshine AI Community License). Consumers that read this catalog receive the stale labels; this report concerns factual metadata, without interpreting license terms.

Runtime or environment

  • Package: @handy-computer/models latest npm release 0.2.3; its tarball integrity matched the npm registry, and its parsed catalog.json was identical to the default-branch catalog.
  • Default branch: main at 2d77f8810ee9539a90328a4c59b420326b225d39; packages/models/curation.yaml pins transcribe.cpp v0.4.0, and the catalog records transcribeCpp: "0.4.0".
  • Comparison source: transcribe.cpp latest release v0.4.1, commit 4d7c1ccefd39e5a9ea36cca5f8fefc6dcc14b99b.
  • Proposed update: open PR models: transcribe.cpp 0.4.2 (0.2.4) #6, head 2632b12423c3d926a4c94f9ec20254bbcc5d2457.
  • Verification: downloaded and parsed the published package and read both repositories in isolated clones. This data mismatch does not depend on a transcription runtime; no model inference or application UI was run.

Steps to reproduce

  1. Download the package tarball and check out the two source baselines stated above. The following commands were executed, with all outputs kept in a disposable working directory:
curl -fsSL https://registry.npmjs.org/@handy-computer/models/-/models-0.2.3.tgz -o models.tgz
mkdir npm-package
tar -xzf models.tgz -C npm-package
git clone https://github.com/handy-computer/models.git models
git clone --filter=blob:none --no-checkout https://github.com/handy-computer/transcribe.cpp.git transcribe
  1. Parse npm-package/package/catalog.json and models/packages/models/catalog.json; compare their models entries by id. They contain the same 76 models and license values.
  2. List catalog/*.json at the comparison release using git -C transcribe ls-tree -r --name-only v0.4.1 catalog. Read each model record with git show, match published_repo's repository basename with the trailing -gguf removed to the package's id, and compare the package's license with the upstream license.spdx. Every package model matched an upstream record; the complete differing set is below.
  3. Inspect the proposed update's catalog diff. It changes all 14 differing labels to the comparison source's values, but those changes are absent from both tested package baselines.

Expected behavior

Consumers of the published model catalog should receive factual license labels reflecting the already-corrected upstream metadata for these models. The package README identifies transcribe.cpp as the source of license facts and directs factual corrections there; that upstream correction is already merged. The README also deliberately ties catalog generation to the engine version apps ship. This report does not claim that pinning an older engine is itself a bug or require a particular engine upgrade; the observable problem is the incorrect labels still delivered to consumers.

Actual behavior

The executed comparison found exactly these 14 differences; the other 62 catalog entries matched the comparison release's license.spdx values:

Model id Published and main license Corrected upstream license.spdx Upstream display name
parakeet-unified-en-0.6b cc-by-4.0 other NVIDIA Open Model License
whisper-large-v3-turbo apache-2.0 mit MIT
moonshine-base-ar mit other Moonshine AI Community License
moonshine-base-ja mit other Moonshine AI Community License
moonshine-base-ko mit other Moonshine AI Community License
moonshine-base-uk mit other Moonshine AI Community License
moonshine-base-vi mit other Moonshine AI Community License
moonshine-base-zh mit other Moonshine AI Community License
moonshine-tiny-ar mit other Moonshine AI Community License
moonshine-tiny-ja mit other Moonshine AI Community License
moonshine-tiny-ko mit other Moonshine AI Community License
moonshine-tiny-uk mit other Moonshine AI Community License
moonshine-tiny-vi mit other Moonshine AI Community License
moonshine-tiny-zh mit other Moonshine AI Community License

For Parakeet Unified English, the original NVIDIA and Handy GGUF Hugging Face API cards independently both report license: other and license_name: nvidia-open-model-license. The catalog generator assigns license: record.license.spdx, explaining how the older source label reaches consumers.

The downstream T3 Code bundled catalog also records source: "@handy-computer/models", sourceVersion: "0.2.3", and engineVersion: "0.4.1", while retaining cc-by-4.0 for this Parakeet model. This is a source-data observation, not a claim about a running application or other consumers' engine versions.

Evidence

The generator's assignment takes the license from the pinned upstream record. The upstream Parakeet record supplies the corrected identifier and display name. Both the original model card API and GGUF model card API confirm that label. The downstream source catalog demonstrates propagation beyond this repository.

Restoration check

Repeat the comparison against a newly published package and the default branch. Each of the 14 listed models should expose the corrected license identifier. Keep the other 62 models as controls, and preserve valid download pins and intentional engine compatibility and recommendation behavior. A corrected PR alone does not establish that published consumers receive the corrected catalog.

References

  • Open update PR #6 already contains all 14 corrections, alongside download pins, minimum-engine changes, benchmark results, seven recommendation changes, two Granite family-name corrections, and the package version bump. The separate update job passed; the current head's pull-request workflow reports action_required, with no maintainer review or explanatory discussion found. This issue tracks the remaining published metadata outcome, rather than requesting a comment or changes on that PR.
  • Merged upstream correction, transcribe.cpp PR #214, fixes the upstream labels.
  • Closed upstream issue, transcribe.cpp #206, documents the original mismatch. Its upstream scope was corrected; the package baselines above still carry the earlier labels.

Triage assessment

  • Impact level: P2
  • Assessment status: supported
  • Impact basis: A consumer-facing metadata field supplies incorrect license identifiers for 14 models, and a downstream bundled catalog demonstrably copies one of them. This affects the reliability of license information presented to model users; no legal outcome, commercial-use decision, or runtime failure was measured.
  • Workaround status: available
  • Workaround basis: Users checking a model's license can consult the corrected upstream catalog and original model card directly. This supplies the factual metadata today, while leaving the package-provided labels stale until corrected publication.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions