dab2020/JF-secure

JF-Secure is a Windows-based utility designed to configure and manage a reverse proxy for Jellyfin using the Caddy web server. The system automates the installation of dependencies, service management, and initial configuration through a console-based setup wizard. It provides a complete installation package and service wrapper to handle the reverse proxy environment on Windows.

The JF-Secure application is introduced, providing a Windows-based utility for reverse proxying Jellyfin. The software features a console-based setup wizard that collects user input for domain names, server URLs, and optional DuckDNS configuration. It automates the installation and startup of the Caddy web server and NSSM service manager to manage the reverse proxy environment.

JF-Secure · high confidence

Added a new NSIS-based Windows installer (installer.nsi) for JF-Secure 3.1, which packages the application executable, supporting binaries (caddy.exe, nssm.exe), and license files, and configures automatic shortcuts and registry entries for installation and uninstallation.

Installer · high confidence

The JF Secure RW application has been rewritten, introducing a new first-time setup wizard (FirstTimeSetup) that guides users through initial configuration, including entering a domain and Jellyfin URL. The application now manages a background service using WinSSW (Windows Service Wrapper) to run Caddy as a service, replacing the previous NSSM-based approach. Users can now perform a one-time setup, create backups of the Caddy configuration, and uninstall the service cleanly. The project structure includes new configuration files (App.config, project-colors.json) and assembly metadata (AssemblyInfo.vb) for version 4.0.0.0.

JF Secure RW · high confidence

Added the Visual Basic project files (\.vbproj\) for the \JF Secure RW\ and \JF-Secure\ applications. These files define the build configuration, references, and build targets for the respective projects, establishing the foundation for compiling the software.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 44 → 37 (-7.2)
• Rubric changed (rubric-2026.08.18 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (+0.0)
• Architecture 69 → 69 (+0.0)
• Maturity 47 → 47 (+0.0)
• Readiness 23 → 12 (-11.2)
• Security 85 → 65 (-20.0)

• Build did not complete in the analyzer
• Monorepo: only 1 of 2 solutions was scored
• No exposed public API
• XML-doc coverage: JF Secure RW (JF Secure RW/JF Secure RW.vbproj)
• early-stage repository — too little history to judge knowledge freshness
• single-maintainer — knowledge-concentration (bus factor) risk

• Documentation: no installation or build instructions (README.md)
• High secret: WD-SECRET-0004 (JF Secure RW/Dab2020.pfx)
• High secret: WD-SECRET-0004 (JF Secure RW/JF Secure RW_TemporaryKey.pfx)
• High secret: WD-SECRET-0004 (JF-Secure/Dab2020.pfx)
• High secret: WD-SECRET-0004 (JF-Secure/JF-Secure_TemporaryKey.pfx)
• Leaked secret: private-key-store (JF Secure RW/Dab2020.pfx)
• Leaked secret: private-key-store (JF Secure RW/JF Secure RW_TemporaryKey.pfx)
• Leaked secret: private-key-store (JF-Secure/Dab2020.pfx)
• Leaked secret: private-key-store (JF-Secure/JF-Secure_TemporaryKey.pfx)
• No ADRs found

• Unchanged — 1 containers · 0 contexts · 0 edges

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

dab2020/JF-secure was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.