github.com/gpakosz/.tmux ↗
gpakosz/.tmux
scanned 2026-05-28 · git af33f07
No security issues flagged
🟢 Looks clean
All 6 checks ran. Nothing urgent to fix.
Informational scan, not a security audit. How this is computed .
🔑 Leaked secrets ✓ 📦 Vulnerable dependencies ✓ 🧬 Known OSS vulnerabilities ✓ ⚠️ Risky code patterns ✓ ☠️ Malicious dependencies ✓ 🩺 Project health 7
Chat with this repo
Simplify and Visualize This Repo
Self Host this repo
Check out more work of Developer: gpakosz
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 ⓘ none found ✓
Your dependencies cross-checked against the OSV vulnerability database.
Nothing found by this check. ✓
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 ⓘ 7 notes
Maintenance & supply-chain hygiene. A signal about the project — not a vulnerability in your code.
Worth fixing scorecard-overall OpenSSF Scorecard overall: 3.4/10
A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detected
A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Code-Review Code-Review scored 0: Found 0/30 approved changesets -- score normalized to 0
A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Dependency-Update-Tool Dependency-Update-Tool scored 0: no update tool detected
A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Fuzzing Fuzzing scored 0: project is not fuzzed
A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-SAST SAST scored 0: no SAST tool detected
A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Security-Policy Security-Policy scored 0: security policy file not detected
A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
via OpenSSF Scorecard v5.5.0 · 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.