gitsafehub
github.com/hongquan/vistickedword ↗

hongquan/vistickedword

scanned 2026-08-06 · git c936d33
2 of 6 checks flagged a security issue
🟡 Worth a look
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets✓Vulnerable dependencies1Known OSS vulnerabilities7Risky 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ⓘ 1 found

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

  • Worth fixing CVE-2024-5569 github.com/jaraco/zipp: Denial of Service (infinite loop) via crafted zip file in jaraco/zipp
    poetry.lock
    A package you depend on has a known security hole (CVE-2024-5569). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 7 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing PYSEC-2020-92 A denial of service via regular expression in the py.path.svnwc component of py (aka python-py) through 1.9.0 could be used by attackers to cause a compute-time denial of service attack by supplying m
    /workdirs/scan-35812b23-6084-4bf1-b218-db3faee0f57f/poetry.lock
    A package you depend on has a known security hole (CVE-2020-29651). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2021-140 An infinite loop in SMLLexer in Pygments versions 1.5 to 2.7.3 may lead to denial of service when performing syntax highlighting of a Standard ML (SML) source file, as demonstrated by input that only
    /workdirs/scan-35812b23-6084-4bf1-b218-db3faee0f57f/poetry.lock
    A package you depend on has a known security hole (CVE-2021-20270). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2021-141 In pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions. Some of the regular expressions have exponential or cubic worst-case complexity an
    /workdirs/scan-35812b23-6084-4bf1-b218-db3faee0f57f/poetry.lock
    A package you depend on has a known security hole (CVE-2021-27291). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2023-117 A ReDoS issue was discovered in pygments/lexers/smithy.py in pygments through 2.15.0 via SmithyLexer.
    /workdirs/scan-35812b23-6084-4bf1-b218-db3faee0f57f/poetry.lock
    A package you depend on has a known security hole (CVE-2022-40896). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1845 pytest has vulnerable tmpdir handling
    /workdirs/scan-35812b23-6084-4bf1-b218-db3faee0f57f/poetry.lock
    A package you depend on has a known security hole (CVE-2025-71176). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2074 zipp Denial of Service vulnerability
    /workdirs/scan-35812b23-6084-4bf1-b218-db3faee0f57f/poetry.lock
    A package you depend on has a known security hole (CVE-2024-5569). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-2987 Pygments has Regular Expression Denial of Service (ReDoS) due to Inefficient Regex for GUID Matching
    /workdirs/scan-35812b23-6084-4bf1-b218-db3faee0f57f/poetry.lock
    A package you depend on has a known security hole (CVE-2026-4539). 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.