License Audit
Hokage Vision Agent License Audit
This audit records the current known license boundaries before restructuring the repository. It is not legal advice.
Initial Findings
- No root
LICENSE,COPYING, orNOTICEfile was found. - The repository originally contained a large amount of upstream-like YOLOv5 source code in the root tree, including
detect.py,train.py,val.py,export.py,hubconf.py,models/,utils/,classify/,segment/, anddata/. This legacy tree has been moved underlegacy/old_project/. - Local file headers and repository history suggest the imported YOLOv5 code is from a GPL-3.0-era YOLOv5 tree. A best-effort comparison against Ultralytics YOLOv5 release tags found the legacy tree is closest to YOLOv5
v7.0:val.py,export.py,models/yolo.py,utils/general.py, andutils/dataloaders.pymatch exactly;train.pyandrequirements.txtare near matches;detect.pyappears locally modified. Treat this as a strong provenance hint, not a complete legal proof. - Git history indicates a root GPL-3.0
LICENSEexisted in the first commit and was later deleted. The legacysetup.cfgnow lives underlegacy/old_project/. - Project-specific legacy files include
base_ui.py,main_window.py,main_window.ui,test_open_image.py,datasets/classes.txt, and readme/demo images underlegacy/old_project/. - The legacy tree includes label files under
legacy/old_project/datasets/labels/and sample images underlegacy/old_project/data/images/, but no source manifest or redistribution statement. These files are retained only as legacy migration evidence and must not be redistributed as an official dataset. - No model weight
.ptfiles were found in the initial large-file scan, but the GUI hardcodesruns/train/exp/weights/best.pt. - The old
libEGL.dllbinary was removed from the current tree because its redistribution terms were not documented. The legacy project documentation records that the old GUI/runtime previously depended on local Qt/OpenGL binary components.
Proposed License Boundaries
- New Hokage Vision Agent source code: Apache-2.0, pending final confirmation that no legacy YOLOv5 source is copied into
src/hokage_vision. - Documentation: CC BY 4.0 may be declared separately if desired.
- Legacy YOLOv5 code: governed by upstream YOLOv5 licensing and isolated under
legacy/old_project/. - Model weights: separately licensed and distributed through releases or manual download scripts only after license review. Current policy for any historical Naruto/Hokage weights is research/portfolio use only, non-commercial, and not redistributed until provenance is documented.
- Dataset images: not redistributed unless rights are verified. Locally captured or user-provided Naruto/Hokage screenshots should be treated as user-provided research material, not as openly licensed public data.
- Dataset annotations: separately licensed only after corresponding image rights are reviewed. Legacy annotations should not be advertised as a reusable public dataset.
Risk Items Requiring Human Confirmation
- Exact upstream YOLOv5 commit/version used as the base of this repository. Best-effort evidence points to YOLOv5
v7.0, but the original import commit/tag was not recorded. - Whether any project-specific files include copied YOLOv5 code beyond normal imports.
- Legal status and redistribution permission for any Naruto/Hokage dataset images used to produce
legacy/old_project/datasets/labels/. Current project policy is no redistribution and no commercial use. - Legal status of
legacy/old_project/readme_images.pngandlegacy/old_project/readme_images/PixPin_2024-05-30_09-03-06.gif. - Whether any old binary runtime dependency can be redistributed. The previously tracked
libEGL.dllhas been removed from the current tree. - Whether old notebooks contain embedded outputs or assets that should be removed or isolated.
- Exact license for the historical YOLOv5 version imported here, including whether GPL-3.0 is the correct governing license for the retained legacy snapshot.
Required Follow-up
- Keep the Apache-2.0
LICENSEscoped to newly written Hokage Vision Agent code until legacy isolation is complete. - Keep
LICENSES/README.mdupdated with source, docs, legacy, data, annotations, model weights, and binary asset boundaries. - Preserve or reference the applicable upstream YOLOv5 license for legacy code.
- Keep
THIRD_PARTY_NOTICES.mdupdated as dependencies are introduced.