chore: fix security.txt

[SunDevil311]

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Security

• Converted static/.well-known/security.txt to an inline PGP clear-signed file and removed the retired detached security.txt.asc signature.

Checklist

• I have read and followed the guidelines in the CONTRIBUTING document.
• I've checked for existing Pull Requests for the same update/change.
• My code follows the project’s coding style.
• My code has been linted locally before submission.
• All new and existing tests pass.

 

• I have updated the documentation accordingly.
• I have added tests to cover my changes, if applicable. (Optional, especially for new contributors)

Pull requests are part of a collaborative process — we welcome contributions and review each one carefully. For all but the smallest changes, you can expect maintainers to request improvements or clarifications.

Please check back after opening your PR and be responsive to feedback so we can get your contribution merged quickly.

Thanks for helping improve Network Pro Strategies!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
web	Ready	Preview	May 28, 2026 3:44am

[SunDevil311]

All files look good. Merging pending successful completion of tests.

[github-actions]

⚠️ Lighthouse Budget Issues Detected

• First Contentful Paint (score: 0.87)
• Largest Contentful Paint (score: 0.43)
• Speed Index (score: 0.95)
• Time to Interactive (score: 0.85)
• Preconnect to required origins (score: 0)
• Largest Contentful Paint element (score: 0)
• Links rely on color to be distinguishable. (score: 0)
• Serve static assets with an efficient cache policy (score: 0.5)
• Reduce unused CSS (score: 0)
• Reduce unused JavaScript (score: 0)
• Use efficient cache lifetimes (score: 0)
• LCP request discovery (score: 0)
• Network dependency tree (score: 0)
• Render blocking requests (score: 0.5)

View the full report in the workflow artifacts or in .lighthouseci/report.html.