NodeValid

Published video-model weights, licences and hardware notes

Acceptable-use policy, beside a licence

An acceptable-use policy is a file that lists uses a publisher forbids. It can accompany a standard permissive licence, which means the badge on a repository does not tell a reader whether one exists. As of 2026-09-22.

Where a use restriction can hide beside a licenceA repository can carry a recognised licence name and a separate file that narrows what the weights may be used for, and the badge shows only the first.Visible from the front pageOnly in the file listLicence nameShown as a badge—Use restrictions—A separate policy fileAttribution termsImplied by the name—Field-of-use limits—Sometimes in the same policyLook beside the licence, not just at it
Fig. 1 Two files, one visible badge, and the restriction in the file nobody looks for.
Files worth checking beside a licence, and what each can carry. Recorded 2026-09-22.
FileWhat it can add
Acceptable useUses the publisher forbids outright
Model cardStated limitations and intended use
NoticeAttribution or trademark conditions
Terms of serviceApplies to a hosted interface, not to weights

Inclusion rule. Files that can change what a reader may do with published weights. A file that only documents behaviour is listed too, because it is routinely mistaken for terms. Order. By how directly the file restricts use, most direct first.

1The badge is not the whole answer

A repository with a standard licence and no extra policy is a different object from one that has both, and the two look identical at a glance. The practical habit is to read the file list rather than stopping at the licence.

This register records the licence name because that is what the vendor published in that field. It does not claim the name is the complete set of conditions.

2A policy is not always enforceable in the same way

Whether a use restriction attached to a weights release binds a particular party in a particular place is a legal question, and it depends on the licence structure as much as on the policy text.

Nothing in this register is a reading of anyone's obligations. What it can do is point at the page and the date, so the question starts from the right document.

3Why the register cannot record this

The licence column holds the value the vendor put in the licence field. A separate policy file is a different document, and the register does not claim the licence name is the complete set of conditions attached to a release.

That is a deliberate limit on the entry rather than an omission. Reading the file list beside a licence is a step the register can recommend and cannot do on a reader's behalf.

A reading note, not an entry: no vendor value appears on this page. Where the register records this term for a particular release, it is on the licence column and on that family's own page. Nearby terms: Redistribution, Derivative weights.