Scan Date: 2026-10-26 09:23:04 UTC Tool Version: v0.1.0
Total repositories scanned: 10 Repositories with issues: 8 Total issues found: 0
| Repository | Total Issues | Critical | High | Medium | Low | Status |
|---|---|---|---|---|---|---|
| JuliusBrussee/caveman | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| avelino/awesome-go | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| fatedier/frp | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| gohugoio/hugo | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| infiniflow/ragflow | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| kubernetes/kubernetes | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| ollama/ollama | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| syncthing/syncthing | 0 | 0 | 0 | 0 | 0 | ✓ Clean |
| Rule ID | Description | Severity | Count | CWE |
|---|
- Immediate Review: All CRITICAL severity issues should be reviewed immediately
- Remediation Plan: Create tickets for HIGH severity issues
- Security Best Practices:
- Never hardcode cryptographic keys
- Use crypto/rand for IV/nonce generation
- Replace MD5/SHA1 with SHA-256 or stronger
- Consider post-quantum cryptography for long-term secrets
- Review all CRITICAL findings
- Patch hardcoded keys immediately
- Update cryptographic algorithms
- Implement secure key management
- Run follow-up scan after remediation
Report generated by CryptoGuard-Go - Automated Cryptographic Vulnerability Scanner For questions or issues, please visit: https://github.com/ravisastryk/cryptoguard-go/issues