github.com/luanvdw/prisma-hackernews-app ↗
luanvdw/prisma-hackernews-app
scanned 2026-08-12 · git 8ad3523
1 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 secrets ✓ 📦 Vulnerable dependencies ✓ 🧬 Known OSS vulnerabilities 1 ⚠️ Risky code patterns ✓ ☠️ Malicious dependencies — 🩺 Project health —
Chat with this repo
Simplify and Visualize This Repo
Self Host this repo
Check out more work of Developer: luanvdw
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 ⓘ 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 ⓘ 1 found
Your dependencies cross-checked against the OSV vulnerability database.
Minor GHSA-73rr-hh4g-fpgx jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch
/workdirs/scan-4cd9032c-c5cc-4686-a14f-0c74095a5f2f/package-lock.json
A package you depend on has a known security hole (CVE-2026-24001). 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.