gitsafehub
github.com/dev-dibster/reviewbot-better ↗

dev-dibster/reviewbot-better

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

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

Leaked secretsVulnerable dependencies4Known OSS vulnerabilities12Risky code patternsMalicious dependenciesProject 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 4 found

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

  • Worth fixing CVE-2026-13676 fast-uri: fast-uri: Security policy bypass due to improper Unicode hostname canonicalization
    pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-13676). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-16221 Impact: fast-uri versions from 2.3.1 through 4.1.0 (including the 3.x ...
    pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-16221). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-18446 fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority
    pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-18446). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-47219 find-my-way: DDoS with HTTP2
    pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-47219). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 12 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-3jxr-9vmj-r5cp brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groups
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-13149). Fix: Update that package to its patched version.
  • Worth fixing GHSA-mh99-v99m-4gvg brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-14257). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rgw5-rvv9-x895 brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-69152). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4c8g-83qw-93j6 fast-uri vulnerable to host confusion via failed IDN canonicalization
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-13676). Fix: Update that package to its patched version.
  • Worth fixing GHSA-7p8r-x3mc-p8w7 fast-uri vulnerable to host confusion via backslash authority introducer
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-18446). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v2hh-gcrm-f6hx fast-uri vulnerable to host confusion via literal backslash authority delimiter
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-16221). Fix: Update that package to its patched version.
  • Worth fixing GHSA-c96f-x56v-gq3h find-my-way: DDoS with HTTP2
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-47219). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4cwx-7wf7-3272 undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-13697). Fix: Update that package to its patched version.
  • Worth fixing GHSA-8xcm-r25x-g524 undici vulnerable to downstream response desynchronization via retry interceptor
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-16728). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jr45-8vmc-qm54 undici vulnerable to cross-user information disclosure via whitespace around equals in Cache-Control directives
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-14643). Fix: Update that package to its patched version.
  • Worth fixing GHSA-m8rv-5g2x-5cg5 undici vulnerable to CRLF Injection via blob-like body 'type' property
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-15157). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v3r7-h72x-cjcm undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields
    /workdirs/scan-9a53f40c-3b2d-451a-8e51-0d03ad618524/pnpm-lock.yaml
    A package you depend on has a known security hole (CVE-2026-16729). 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 timed out

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

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

via Guarddog v2.10.0 · Apache-2.0

error: npm:timeout

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.