Update metadata.json for WiFi Brute Force theme with correct name, de…

[emericklaw]

…scription, and version

[github-actions]

❌ Validation Failed

📦 Apps/Components Being Updated:

RF Brute Force (repositories/BruceDevices/firmware/RF Brute Force)

✅ Validation Passed

• Repository: BruceDevices/firmware
• Path: /sd_files/interpreter/
• Version: 1.0.1 → 1.0.3 (✅ Version updated)
• Category: RF
• Changes: View commit comparison

🔍 Validation Steps (click to expand)

• 📄 metadata.json
  • ✅ File exists
  • ✅ Valid JSON format
  • 🔍 Checking required fields...
    • ✅ Field name: RF Brute Force
    • ✅ Field category: RF
    • ✅ Field description: Brute force RF signals
    • ✅ Field version: 1.0.3
    • ✅ Field commit: 18fe3c2c994c6a276447b2aee84e310c837ccbc4
    • ✅ Field owner: BruceDevices
    • ✅ Field repo: firmware
    • ✅ Field path: /sd_files/interpreter/
  • 🔍 Validating fields...
    • ✅ Version format valid: 1.0.3
    • ✅ Commit hash format valid: 18fe3c2c994c6a276447b2aee84e310c837ccbc4...
    • ✅ Commit 18fe3c2c994c6a276447b2aee84e310c837ccbc4... exists on GitHub
    • ✅ Category valid: RF
  • 🔍 Checking folder structure...
    • ✅ Folder structure valid: contains repositories/BruceDevices/firmware
  • 🔍 Validating files array...
    • ✅ Files field is a valid array with 1 entries
    • 🔍 Fetching repository file tree...
    • ✅ Repository tree loaded (1121 files)
    • ✅ File exists at commit: rf_brute.js → RF Brute Force.js (path: sd_files/interpreter/rf_brute.js)
  • 🔍 Checking version history...
    • 🔍 Current version: 1.0.3
    • ✅ Found previous file in main branch
    • 📋 Previous version: 1.0.1
    • ✅ Version updated: 1.0.1 → 1.0.3
  • ✅ All validation checks passed
    • 🔍 Compare link check:
      • Previous commit: c9d3731b...
      • Current commit: 18fe3c2c...
      • Owner/Repo: BruceDevices/firmware
      • ✅ Compare link generated: BruceDevices/firmware@c9d3731...18fe3c2
  • 📄 logo.png
    • ✅ File exists
    • 🔍 Checking logo dimensions...
      • ℹ️ Logo size: 128x128
      • ✅ Logo size valid: 128x128

WiFi Brute Force (repositories/BruceDevices/firmware/WiFi Brute Force)

❌ Validation Failed

• Repository: BruceDevices/firmware
• Path: /sd_files/interpreter/
• Version: 1.0.2 → 1.0.3 (❌ Same commit)
• Category: WiFi

🔍 Validation Steps (click to expand)

• 📄 metadata.json
  • ✅ File exists
  • ✅ Valid JSON format
  • 🔍 Checking required fields...
    • ✅ Field name: WiFi Brute Force
    • ✅ Field category: WiFi
    • ✅ Field description: Brute force WiFi network password with dictionary attack
    • ✅ Field version: 1.0.3
    • ✅ Field commit: 18fe3c2c994c6a276447b2aee84e310c837ccbc4
    • ✅ Field owner: BruceDevices
    • ✅ Field repo: firmware
    • ✅ Field path: /sd_files/interpreter/
  • 🔍 Validating fields...
    • ✅ Version format valid: 1.0.3
    • ✅ Commit hash format valid: 18fe3c2c994c6a276447b2aee84e310c837ccbc4...
    • ✅ Commit 18fe3c2c994c6a276447b2aee84e310c837ccbc4... exists on GitHub
    • ✅ Category valid: WiFi
  • 🔍 Checking folder structure...
    • ✅ Folder structure valid: contains repositories/BruceDevices/firmware
  • 🔍 Validating files array...
    • ✅ Files field is a valid array with 1 entries
    • 🔍 Fetching repository file tree...
    • ✅ Repository tree loaded (1121 files)
    • ✅ File exists at commit: wifi_brute.js → WiFi Brute Force.js (path: sd_files/interpreter/wifi_brute.js)
  • 🔍 Checking version history...
    • 🔍 Current version: 1.0.3
    • ✅ Found previous file in main branch
    • 📋 Previous version: 1.0.2
    • ❌ Commit must be updated: 18fe3c2c994c6a276447b2aee84e310c837ccbc4... is same as previous commit
    • 🔍 Compare link check:
      • Previous commit: 18fe3c2c...
      • Current commit: 18fe3c2c...
      • Owner/Repo: BruceDevices/firmware
      • ℹ️ Commits are identical, no changes to compare
      • 🚫 No compare link generated
  • 📄 logo.png
    • ✅ File exists
    • 🔍 Checking logo dimensions...
      • ℹ️ Logo size: 128x128
      • ✅ Logo size valid: 128x128

Summary of Issues:

❌ Invalid metadata.json files detected

Please fix the errors shown in the 🔍 Validation Steps output above.

Please address the above issues and push new commits to this pull request for re-validation.

Please check the documentation for guidance on resolving validation errors here.