github.com/marcobambini/gravity ↗
marcobambini/gravity
scanned 2026-06-30 · git 3744550
Scan didn’t finish
⚪ Only 0 of 6 checks ran
That’s not enough to judge this repo — so we’re not showing a verdict. A green “safe” here would be misleading.
Check again ↻
Informational scan, not a security audit. How this works .
🔑 Leaked secrets — 📦 Vulnerable dependencies — 🧬 Known OSS vulnerabilities — ⚠️ 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: marcobambini
Security checks
🔑 Leaked secrets — Gitleaks ⓘ didn’t run
API keys, passwords or tokens committed into the repo.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
via Gitleaks · MIT
📦 Vulnerable dependencies — Trivy ⓘ didn’t run
Packages you depend on that have known security holes (CVEs).
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
via Trivy · Apache-2.0
🧬 Known OSS vulnerabilities — OSV-Scanner ⓘ didn’t run
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 · Apache-2.0
⚠️ Risky code patterns — Semgrep ⓘ didn’t run
Code that can be exploited — injection, hardcoded credentials and similar.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
via Semgrep · LGPL-2.1
☠️ Malicious dependencies — Guarddog ⓘ didn’t run
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 · 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.