gitsafehub
github.com/bdemers/shiro-angular-example ↗

bdemers/shiro-angular-example

scanned 2026-08-16 · git 03b9c1d
1 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets✓Vulnerable dependencies19Known OSS vulnerabilities—Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 19 found · 2 serious

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

  • Serious CVE-2017-5929 logback: Serialization vulnerability in SocketServer and ServerSocketReceiver
    pom.xml
    A package you depend on has a known security hole (CVE-2017-5929). Fix: Update that package to its patched version.
  • Serious CVE-2017-5929 logback: Serialization vulnerability in SocketServer and ServerSocketReceiver
    pom.xml
    A package you depend on has a known security hole (CVE-2017-5929). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-6378 logback: serialization vulnerability in logback receiver
    pom.xml
    A package you depend on has a known security hole (CVE-2023-6378). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-6378 logback: serialization vulnerability in logback receiver
    pom.xml
    A package you depend on has a known security hole (CVE-2023-6378). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-42550 logback: remote code execution through JNDI call from within its configuration file
    pom.xml
    A package you depend on has a known security hole (CVE-2021-42550). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-12798 logback-core: arbitrary code execution via JaninoEventEvaluator
    pom.xml
    A package you depend on has a known security hole (CVE-2024-12798). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-11226 ch.qos.logback/logback-core: Conditional abitrary code execution in logback-core
    pom.xml
    A package you depend on has a known security hole (CVE-2025-11226). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-29131 commons-configuration: StackOverflowError adding property in AbstractListDelimiterHandler.flattenIterator()
    pom.xml
    A package you depend on has a known security hole (CVE-2024-29131). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-29133 commons-configuration: StackOverflowError calling ListDelimiterHandler.flatten(Object, int) with a cyclical object tree
    pom.xml
    A package you depend on has a known security hole (CVE-2024-29133). Fix: Update that package to its patched version.
  • Worth fixing CVE-2016-10735 bootstrap: XSS in the data-target attribute
    pom.xml
    A package you depend on has a known security hole (CVE-2016-10735). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-14040 bootstrap: Cross-site Scripting (XSS) in the collapse data-parent attribute
    pom.xml
    A package you depend on has a known security hole (CVE-2018-14040). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-14042 bootstrap: Cross-site Scripting (XSS) in the data-container property of tooltip
    pom.xml
    A package you depend on has a known security hole (CVE-2018-14042). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-20676 bootstrap: XSS in the tooltip data-viewport attribute
    pom.xml
    A package you depend on has a known security hole (CVE-2018-20676). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-20677 bootstrap: XSS in the affix configuration target property
    pom.xml
    A package you depend on has a known security hole (CVE-2018-20677). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-8331 bootstrap: XSS in the tooltip or popover data-template attribute
    pom.xml
    A package you depend on has a known security hole (CVE-2019-8331). Fix: Update that package to its patched version.
  • Minor CVE-2024-12801 logback-core: SaxEventRecorder vulnerable to Server-Side Request Forgery (SSRF) attacks
    pom.xml
    A package you depend on has a known security hole (CVE-2024-12801). Fix: Update that package to its patched version.
  • Minor CVE-2026-10532 Deserialization of untrusted data vulnerability in QOS.CH Sarl logback ...
    pom.xml
    A package you depend on has a known security hole (CVE-2026-10532). Fix: Update that package to its patched version.
  • Minor CVE-2026-1225 ch.qos.logback/logback-core: Malicious logback.xml configuration file allows instantiation of arbitrary classes
    pom.xml
    A package you depend on has a known security hole (CVE-2026-1225). Fix: Update that package to its patched version.
  • Minor CVE-2026-9828 Deserialization of untrusted data vulnerability in QOS.CH Sarl logback ...
    pom.xml
    A package you depend on has a known security hole (CVE-2026-9828). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

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

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 120s

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.