gitsafehub
github.com/deepset-ai/hayhooks ↗

deepset-ai/hayhooks

scanned 2026-08-03 · git 8027661
3 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 secrets3Vulnerable dependencies35Known OSS vulnerabilitiesRisky code patternsMalicious dependencies2Project health

Security checks

Leaked secrets — Gitleaks 3 found · 3 serious

API keys, passwords or tokens committed into the repo.

  • Serious curl-auth-header Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
    examples/programmatic/api_key_auth/README.md:66
    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 curl-auth-header Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
    examples/programmatic/api_key_auth/README.md:76
    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 curl-auth-header Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
    examples/programmatic/api_key_auth/README.md:85
    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 35 found

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

  • Worth fixing GHSA-frvp-7c67-39w9 Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)
    dashboard/package-lock.json
    A package you depend on has a known security hole (GHSA-frvp-7c67-39w9). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-13149 brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-13149). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-14257 brace-expansion through 5.0.7 is vulnerable to denial of service via m ...
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-14257). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-45149 brace-expansion: brace-expansion: Denial of Service due to excessive memory allocation when expanding large numeric ranges
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-45149). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-13676 fast-uri: fast-uri: Security policy bypass due to improper Unicode hostname canonicalization
    dashboard/package-lock.json
    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 ...
    dashboard/package-lock.json
    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-6321 fast-uri: fast-uri: Path traversal vulnerability allows bypass of security policies
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-6321). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-6322 fast-uri: fast-uri: URI authority bypass due to improper delimiter handling
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-6322). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54290 hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54290). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-44455 hono/jsx has Unvalidated JSX Tag Names that May Allow HTML Injection
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-44455). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-44456 Hono: bodyLimit() can be bypassed for chunked / unknown-length requests
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-44456). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-44457 Hono's Cache Middleware ignores Vary: Authorization / Vary: Cookie leading to cross-user cache leakage
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-44457). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-44458 Hono has CSS Declaration Injection via Style Object Values in JSX SSR
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-44458). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-47673 Hono: JWT middleware accepts any Authorization scheme, not only Bearer
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-47673). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-47674 Hono: IP Restriction bypasses static deny rules for non-canonical IPv6
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-47674). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-47675 Hono: Cookie helper does not sanitize sameSite and priority, allowing Set-Cookie injection
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-47675). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-47676 Hono: app.mount() strips mount prefix using undecoded path, causing incorrect routing for percent-encoded paths
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-47676). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54286 hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54286). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54287 hono: AWS Lambda adapter merges multiple `Set-Cookie` headers into one value, dropping cookies on ALB single-header and Lattice
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54287). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54288 hono: Body Limit Middleware can be bypassed on AWS Lambda by understating `Content-Length`
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54288). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54289 hono: Lambda@Edge adapter keeps only the last value of a repeated request header, dropping the rest
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54289). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-59895 hono: Hono: Arbitrary markup injection via improper handling of class names in server-side rendering.
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59895). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-59896 hono: Hono: Information disclosure due to improper context isolation in server-side rendering
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59896). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-59897 hono: Hono: Information disclosure due to incorrect header de-duplication in AWS API Gateway v1 adapter
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59897). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-42338 ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input
    dashboard/package-lock.json
    A package you depend on has a known security hole (CVE-2026-42338). Fix: Update that package to its patched version.
… 10 more not shown

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 400s

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 2 found

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

  • Worth fixing guarddog-pypi-shady-links shady-links match in mcp 2.0.0
    mcp
    A dependency shows signs of being intentionally malicious (typosquat, hidden install script, etc.). Fix: Don’t install it until you’ve verified the package. Consider removing it.
  • Worth fixing guarddog-pypi-obfuscation obfuscation match in haystack-ai 3.1.0.dev20260803001922
    haystack-ai
    A dependency shows signs of being intentionally malicious (typosquat, hidden install script, etc.). Fix: Don’t install it until you’ve verified the package. Consider removing it.

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.