1.7 KiB
1.7 KiB
FamiliarOS Repo License Tracking
Last updated: 2026-06-18
| Source | Scope | License / Rights Read | Confidence | Route | Notes |
|---|---|---|---|---|---|
FamiliarOS |
first-party repo code | MIT (/home/dev/src/FamiliarOS/LICENSE) |
high |
direct first_party_owner |
Current repo code is clearly MIT licensed. |
alvinunreal/openpets |
upstream code lineage | MIT (repo + homepage statements) | high |
direct lineage / bounded review |
Code license is permissive and compatible with the existing FamiliarOS fork history. |
OpenPets catalog/community familiar assets |
distributed familiar packs and gallery media | mixed / pack-specific / not automatically covered by code MIT | medium |
replace_or_verify_pack_by_pack |
OpenPets legal and terms pages explicitly state some familiars may be unofficial fan-made content and rights remain with respective owners. Do not assume gallery familiars are safe for FamiliarOS redistribution without pack-specific rights confirmation. |
ScriptoriumAI root .gitnexus state |
repo-local analysis index, not product runtime | repo-specific generated state | high |
scaffold_only / regenerate_locally |
The Scriptorium root .gitnexus data points at C:\ScriptoriumAI; it is not safe to treat as a valid FamiliarOS index. Use only as workflow reference and regenerate repo-local state. |
Operational Rule
When code license and asset rights diverge, the stricter surface wins for the asset-distribution question.
That means FamiliarOS may continue code-side lineage work while still treating legacy OpenPets familiar packs as replace-or-verify material instead of automatic first-party FamiliarOS assets.