What happened
A BeefTV repository commit dated October 19, 2026 replaces the project’s prior license presentation with a two-part licensing document. Part A is titled the BeefTV Source Available License 1.0; Part B retains the prior MIT license text and notices. GitHub consequently identifies the repository license as “Other,” rather than MIT.
The central boundary is temporal and material-specific. The new Part A applies to “new, original BeefTV-authored material” first made available under the license beginning with the commit that introduced it, as well as later original contributions submitted under that license, unless a file or component notice says otherwise. It applies only where a copyright holder is entitled to grant those rights.
The license explicitly preserves historical permissions. Material previously made available under MIT remains available under MIT, including material in two cited earlier commits and any other material previously published under MIT. The text says Part A does not revoke, replace, or restrict those existing permissions, even if old MIT material appears in a later release. Where a file mixes historical material and new original additions, Part A applies only to the eligible new additions.
Part A excludes third-party code, dependencies, models, fonts, assets, and other independently licensed material; those retain their own terms. It also excludes material whose distribution must be governed by GPL or another incompatible license. The document warns that this exclusion does not itself make a combined distribution compatible: distributors still need to satisfy all applicable licenses and obtain compatible permissions where needed.
The new license defines an “External Service” broadly as giving a third party access to operate, interact with, or invoke covered material or a derivative work, including through a hosted application, managed service, remote desktop, or API. It distinguishes delivery of creative outputs alone from an External Service. This definition matters because a team can use the same code in materially different ways: producing a video output is not itself described as an External Service, while exposing covered material through a hosted interface can be.
The license lists a commercial-authorization contact, and the repository’s accompanying contribution guidance says new original contributions are contributed under Part A by default. Contributors grant the official repository maintainers a non-exclusive, perpetual, irrevocable, worldwide, royalty-free copyright license to copy, modify, distribute, and relicense those contributions under a community license or separate commercial terms. Contributors retain copyright; the contribution guidance says this is not a copyright assignment and does not retroactively apply to historical contributions or third-party material.
What the archive adds
This is a new fact on a known story. Our earlier note, BeefTV is an open-source, MIT-licensed AI video workspace built on an infinite node canvas, described BeefTV as an MIT-licensed workspace. The new commit narrows that characterization for future original code while preserving the earlier MIT grant.
Trend signal
No supplied pattern genuinely fits this licensing event.
Why it matters
For a team merely inspecting or adapting an older BeefTV snapshot, the commit says the previous MIT permissions survive. For a team pulling current releases, operating a hosted variant, or building a commercial service around later original additions, “the repository is MIT” is no longer an adequate compliance conclusion.
The important operational question is not simply which repository version is checked out. It is which portions of that version are historical MIT material, which are covered new additions, and which are third-party components with separate obligations. That creates provenance work for forks, distributions, vendor reviews, and contribution policies. It also changes the contributor bargain: future original contributions can be relicensed by the official maintainers under community or separate commercial terms, while contributors keep their copyright.
This is especially consequential for teams that turn a repository into a service. The stated definition of External Service includes a hosted application, managed service, remote desktop, and API. A deployment review therefore needs to consider both code provenance and the way users access the resulting system, rather than treating a public repository as a single, uniform permission grant.
Limits and uncertainty
The commit establishes the project’s stated terms; it does not establish how those terms would be interpreted or enforced in a specific jurisdiction. It does not provide commercial pricing, a standard commercial agreement, or a practical file-by-file inventory of material covered by Part A. The supplied material also does not show whether all downstream releases will label newly covered files consistently enough for automated compliance review.
This note is not legal advice. Teams planning a hosted product, redistribution, or a commercial derivative should identify the precise code they rely on, preserve relevant provenance, and obtain legal review or commercial authorization where their use may fall within the new terms.
Skill to build now
Add license provenance to dependency review. For a repository with mixed historical and newly relicensed code, record the commit range, relevant file history, third-party notices, and the planned distribution or hosting model. Treat an unqualified repository-level license badge as a starting point, not a complete answer.
Reader takeaway
BeefTV did not retroactively take MIT rights away from earlier code. But new original code is no longer offered under a pure MIT repository-wide posture: it is source-available under Part A, with commercial authorization required. Adoption decisions should be made at the component and version level.
Open question
Will BeefTV publish a practical inventory or release-level marking that makes the boundary between historical MIT material and Part A additions easy for downstream users to audit?