Are the `ltx-core` and `ltx-pipelines` PyPI packages officially published by Lightricks?

Open
#228 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python
Domain
release, security

Research direction

Read the repository README, the HuggingFace model card, and the packages/ directory referenced in the issue, then compare their installation instructions and package metadata with the two PyPI listings. The issue is resolved when a maintainer confirms whether the packages are official; if they are, update the README with the PyPI links and provenance guidance.

Written by the indexing model from the issue text.

Description

Hi! Thanks for open-sourcing LTX-2.

I noticed there are PyPI packages ltx-core and ltx-pipelines (both v1.0.0, uploaded 2026-03-18) whose pyproject.toml and source match the packages/ directory of this repo. However:

  • The READMEs in this repo and the HuggingFace model card only ever instruct pip install -e packages/... from a local clone — no PyPI install line.
  • The PyPI releases have no author/maintainer/project URL metadata, no license, and no PEP 740 attestations linking them to this repo (no .github/workflows/ for Trusted Publishing exists).

Could a maintainer confirm whether Lightricks uploaded these to PyPI, or whether they were published by a third party? If they are official, it would help downstream users if the README linked to the PyPI listings and (ideally) future releases used Trusted Publishing so consumers can verify provenance.

Thanks!

Dominant language
Python
Stars
10k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Lightricks/LTX-2

All issues in Lightricks/LTX-2

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.