gitsafehub
github.com/lover520f/asspp-2026 ↗

lover520f/asspp-2026

scanned 2026-08-07 · git c736de2
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets2Vulnerable dependencies5Known OSS vulnerabilitiesRisky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks 2 found · 2 serious

API keys, passwords or tokens committed into the repo.

  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    Resources/Certificates/localhost.qaq.wiki/rootCA-key.pem:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    Resources/Certificates/localhost.qaq.wiki/localhost.qaq.wiki-key.pem:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivy 5 found

Packages you depend on that have known security holes (CVEs).

  • Worth fixing CVE-2026-28980 SwiftNIO NIOHTTP1: HTTPDecoder accepts unbounded HTTP/1 header blocks, enabling remote DoS
    Asspp.xcworkspace/xcshareddata/swiftpm/Package.resolved
    A package you depend on has a known security hole (CVE-2026-28980). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-43671 SwiftNIO: Out-of-bounds write via ByteBuffer index and length UInt32 overflow
    Asspp.xcworkspace/xcshareddata/swiftpm/Package.resolved
    A package you depend on has a known security hole (CVE-2026-43671). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-28970 SwiftNIO: CRLF Injection in outbound HTTP request URI via NIOHTTPRequestHeadersValidator
    Asspp.xcworkspace/xcshareddata/swiftpm/Package.resolved
    A package you depend on has a known security hole (CVE-2026-28970). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-28975 NIOExtras: NIOHTTPRequestDecompressor ratio limit bypass via inflated Content-Length
    Asspp.xcworkspace/xcshareddata/swiftpm/Package.resolved
    A package you depend on has a known security hole (CVE-2026-28975). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-28898 SwiftNIO HTTP/2: HTTP/2-to-HTTP/1 Request Smuggling via unvalidated :path pseudo-header in HTTP2ToHTTP1Codec
    Asspp.xcworkspace/xcshareddata/swiftpm/Package.resolved
    A package you depend on has a known security hole (CVE-2026-28898). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner none found ✓

Your dependencies cross-checked against the OSV vulnerability database.

Nothing found by this check. ✓

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrep none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddog none found ✓

Packages that look intentionally malicious: typosquats, sneaky install scripts.

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecard didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.