NodeValid

Published video-model weights, licences and hardware notes

Pyramid Flow carries another company's licence

This release is tagged stabilityai-ai-community. The weights were published by a different account from the company the licence is named after, so the name identifies the document rather than the publisher. As of 2026-09-22.

Pyramid Flow in the licence column, as publishedA licence name usually identifies whoever wrote it; here it identifies a document that has been reused by a publisher with no share in the name.What a reader has to do with the file beside these weightsThe name on the filestabilityai-ai-communityA licence name from one company onanother's releaseThe release it travels withNo parameter count recordedThe card states noneThe name is the document, not the author
Fig. 1 Reading the publisher off the licence name gets the wrong company in this row.
What the repositories actually stateFilled where the repository states something, hollow where it does not. A blank is not an inference.What the repositories actually stateWhat the pages stateWhat the pagesstateLicence, in the vendor's own wor…Licence, in the vendor's own wordsLicence, in the vendor's own words — What the pages state: stabilityai-ai-communityThe detail published beside itThe detail published beside it — What the pages state: A licence name from one company on another's releaseSize, from the same pagesSize, from the same pages — What the pages state: No parameter count recorded
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Pyramid Flow in the licence column, with the columns that qualify it. Read from huggingface.co/rain1011 on 2026-09-22.
ColumnWhat the pages state
Licence, in the vendor's own wordsstabilityai-ai-community
The detail published beside itA licence name from one company on another's release
Size, from the same pagesNo parameter count recorded

Inclusion rule. The value this page is about, the detail the vendor attached to it, and the two columns that change how it should be read. A column the vendor left empty keeps its row and says so. Order. This column first, then its detail, then the two columns that qualify it.

1Vendor-written licences travel

Once a company writes terms for its own releases, nothing stops another project applying the same document to its weights. That is how a licence named after one organisation ends up on a release published by an unrelated account.

It also means the document is more widely read than a truly bespoke licence would be, which slightly offsets the cost of it not being a standard one.

2Why this confuses a search

A reader looking up the licence will land on the naming company's pages and its own releases, none of which are this model. Working out which version of that document applies here takes a step that a standard name would not need.

The register records the tag verbatim and links the card it was read from, so the starting point is at least the right page.

3The rest of this card is generous

Whatever the licence situation, the card is informative where it counts for output: two checkpoints, 768p on one and 384p on the other, with the clip length each one produces.

That mix is common. Documentation quality is not uniform across the columns of a release, and a card can be careful about pixels and casual about paperwork.

4Sources

The licence name was read from huggingface.co/rain1011 on 2026-09-22 and is quoted rather than summarised. The rest of this release is on its family entry; how names in this column are handled is on licence. Nearby: skywork-license, Commercial use answered.