Skip to content

Conversation

@sahancz
Copy link

@sahancz sahancz commented Sep 18, 2025

Summary

Vendored YouTube Clip Extraction Tool into the Player-Tracking documentation.

Changes

  • Added `youtube-clip-extraction-tool folder with the original tool:

    • video_processing.py
    • requirements.txt
    • setup.bat
  • Added Redback-specific wrapper docs:

    • README.md → context for Kick, Mark, Tackle annotation workflow
    • USAGE.md → step-by-step usage guide for annotators
    • examples/clips.yaml → AFL sample links (Kick, Mark, Tackle)

Purpose

This ensures annotators can extract 3–6 second clips consistently for CVAT annotation in the Player-Tracking project.
Standardising this workflow saves time and keeps datasets structured.

@sahancz sahancz requested review from a team as code owners September 18, 2025 09:46
@sahancz sahancz closed this Sep 18, 2025
@sahancz sahancz reopened this Sep 18, 2025
@lperry022 lperry022 self-assigned this Sep 26, 2025
@github-actions
Copy link

🔒 OWASP Scanner Results

Vulnerabilities were detected:

### File: docs/project-4/Player-Tracking/Youtube_Clip_Extraction_Tool-main/README.md

🔒 OWASP Scanner Results for docs/project-4/Player-Tracking/Youtube_Clip_Extraction_Tool-main/README.md

✅ No vulnerabilities found.


### File: docs/project-4/Player-Tracking/Youtube_Clip_Extraction_Tool-main/Usage.md

🔒 OWASP Scanner Results for docs/project-4/Player-Tracking/Youtube_Clip_Extraction_Tool-main/Usage.md

✅ No vulnerabilities found.


### File: docs/project-4/Player-Tracking/Youtube_Clip_Extraction_Tool-main/video_processing.py

🔒 OWASP Scanner Results for docs/project-4/Player-Tracking/Youtube_Clip_Extraction_Tool-main/video_processing.py

A09: Security Logging and Monitoring Failures (5 findings)

Summary: MEDIUM: 5

  • Line 125 | Severity MEDIUM | Confidence LOW
    → Exception handled with print() instead of proper logging/alerting near: except Exception as e:
  • Line 216 | Severity MEDIUM | Confidence LOW
    → Exception handled with print() instead of proper logging/alerting near: except Exception as e:
  • Line 260 | Severity MEDIUM | Confidence LOW
    → Exception handled with print() instead of proper logging/alerting near: except ValueError as e:
  • Line 343 | Severity MEDIUM | Confidence LOW
    → Exception handled with print() instead of proper logging/alerting near: except Exception as e:
  • Line 432 | Severity MEDIUM | Confidence LOW
    → Exception handled with print() instead of proper logging/alerting near: except Exception as e:

⛔ Please address these before merging.

@lperry022 lperry022 removed their assignment Sep 26, 2025
@ben-AI-cybersec
Copy link
Member

This includes code, not documentation, please move it to the appropriate repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants