gitsafehub
github.com/winlinvip/jsip ↗

winlinvip/jsip

scanned 2026-08-14 · git 411bc78
2 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 secrets2Vulnerable dependenciesKnown OSS vulnerabilities18Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks 2 found

API keys, passwords or tokens committed into the repo.

  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    src/gov/nist/javax/sip/stack/NioWebSocketMessageChannel.java:153
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    src/gov/nist/javax/sip/stack/NioTlsWebSocketMessageChannel.java:190
    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 couldn’t run

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

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

via Trivy v0.70.0 · Apache-2.0

error: unexpected fault address 0x7f23490fb000 fatal error: fault [signal SIGSEGV: segmentation violation code=0x2 addr=0x7f23490fb000 pc=0x93c06a] goroutine 1 gp=0xc000002380 m=2 mp=0xc0000b4808 [running]: runtime.throw({0x57e6c1e?, 0x0?}) /opt/hostedtoolcache/go/1.25.9/x64/src/runtime/panic.go:1094 +0x

Known OSS vulnerabilities — OSV-Scanner 18 found · 9 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-2qrg-x229-3v8q Deserialization of Untrusted Data in Log4j
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/javax/sip/jain-sip-ri/1.2/jain-sip-ri-1.2.pom
    A package you depend on has a known security hole (CVE-2019-17571). Fix: Update that package to its patched version.
  • Serious GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/javax/sip/jain-sip-ri/1.2/jain-sip-ri-1.2.pom
    A package you depend on has a known security hole (CVE-2022-23305). Fix: Update that package to its patched version.
  • Serious GHSA-f7vh-qwp3-x37m Deserialization of Untrusted Data in Apache Log4j
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/javax/sip/jain-sip-ri/1.2/jain-sip-ri-1.2.pom
    A package you depend on has a known security hole (CVE-2022-23307). Fix: Update that package to its patched version.
  • Serious GHSA-2qrg-x229-3v8q Deserialization of Untrusted Data in Log4j
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/android-jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2019-17571). Fix: Update that package to its patched version.
  • Serious GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/android-jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2022-23305). Fix: Update that package to its patched version.
  • Serious GHSA-f7vh-qwp3-x37m Deserialization of Untrusted Data in Apache Log4j
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/android-jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2022-23307). Fix: Update that package to its patched version.
  • Serious GHSA-2qrg-x229-3v8q Deserialization of Untrusted Data in Log4j
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2019-17571). Fix: Update that package to its patched version.
  • Serious GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2022-23305). Fix: Update that package to its patched version.
  • Serious GHSA-f7vh-qwp3-x37m Deserialization of Untrusted Data in Apache Log4j
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2022-23307). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fp5r-v3w9-4333 JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/javax/sip/jain-sip-ri/1.2/jain-sip-ri-1.2.pom
    A package you depend on has a known security hole (CVE-2021-4104). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vp98-w2p3-mv35 Apache Log4j 1.x (EOL) allows Denial of Service (DoS)
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/javax/sip/jain-sip-ri/1.2/jain-sip-ri-1.2.pom
    A package you depend on has a known security hole (CVE-2023-26464). Fix: Update that package to its patched version.
  • Worth fixing GHSA-w9p3-5cr8-m3jj Deserialization of Untrusted Data in Log4j 1.x
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/javax/sip/jain-sip-ri/1.2/jain-sip-ri-1.2.pom
    A package you depend on has a known security hole (CVE-2022-23302). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fp5r-v3w9-4333 JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/android-jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2021-4104). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vp98-w2p3-mv35 Apache Log4j 1.x (EOL) allows Denial of Service (DoS)
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/android-jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2023-26464). Fix: Update that package to its patched version.
  • Worth fixing GHSA-w9p3-5cr8-m3jj Deserialization of Untrusted Data in Log4j 1.x
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/android-jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2022-23302). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fp5r-v3w9-4333 JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2021-4104). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vp98-w2p3-mv35 Apache Log4j 1.x (EOL) allows Denial of Service (DoS)
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2023-26464). Fix: Update that package to its patched version.
  • Worth fixing GHSA-w9p3-5cr8-m3jj Deserialization of Untrusted Data in Log4j 1.x
    /workdirs/scan-2a10f111-d594-4948-8cf7-3aca1e7081db/m2/jain-sip-ri/pom.xml
    A package you depend on has a known security hole (CVE-2022-23302). Fix: Update that package to its patched version.

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.