gitsafehub
github.com/devinivy/hapi-v7 ↗

devinivy/hapi-v7

scanned 2026-08-07 · git c1f1546
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets5Vulnerable dependenciesKnown OSS vulnerabilities10Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks 5 found · 5 serious

API keys, passwords or tokens committed into the repo.

  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    test/proxy.js:970
    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 private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    test/proxy.js:997
    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 private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    test/proxy.js:1023
    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 private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    test/server.js:340
    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 private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    test/response.js:2573
    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 none found ✓

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

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 10 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-5854-jvxx-2cg9 Denial of Service in content
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-x6wp-rfwh-hcx7 Regular Expression Denial of Service in content
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole (CVE-2017-16111). Fix: Update that package to its patched version.
  • Worth fixing GHSA-c429-5p7v-vgjp hoek subject to prototype pollution via the clone function.
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole (CVE-2020-36604). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jp4x-w63m-7wgm Prototype Pollution in hoek
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole (CVE-2018-3728). Fix: Update that package to its patched version.
  • Worth fixing GHSA-q7cg-457f-vx79 joi has an uncaught RangeError on deeply nested input through recursive `link()` schemas
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole (CVE-2026-48038). Fix: Update that package to its patched version.
  • Worth fixing GHSA-g64q-3vg8-8f93 Prototype Pollution in pez
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-6rw7-vpxm-498p qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustion
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole (CVE-2025-15284). Fix: Update that package to its patched version.
  • Worth fixing GHSA-gqgv-6jq5-jjj9 Prototype Pollution Protection Bypass in qs
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole (CVE-2017-1000048). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hrpp-h998-j3pp qs vulnerable to Prototype Pollution
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole (CVE-2022-24999). Fix: Update that package to its patched version.
  • Worth fixing GHSA-2mvq-xp48-4c77 Denial of Service in subtext
    /workdirs/scan-8c249b7f-bca5-4f7f-85ec-b3c73ded564c/npm-shrinkwrap.json
    A package you depend on has a known security hole. 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.