github.com/timqian/side-project-marketing ↗
timqian/side-project-marketing
scanned 2026-08-04 · git bd0de7a
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 secrets ✓ 📦 Vulnerable dependencies 5 🧬 Known OSS vulnerabilities 5 ⚠️ 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: timqian
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 ⓘ
5 found · 1 serious
Packages you depend on that have known security holes (CVEs).
Serious CVE-2020-14001 rubygem-kramdown: processing template options inside documents allows unintended read access or embedded Ruby code execution
Gemfile.lock
A package you depend on has a known security hole (CVE-2020-14001). Fix: Update that package to its patched version.
Worth fixing CVE-2021-32740 rubygem-addressable: ReDoS in templates
Gemfile.lock
A package you depend on has a known security hole (CVE-2021-32740). Fix: Update that package to its patched version.
Worth fixing CVE-2026-35611 addressable: Addressable: Denial of Service via crafted URI templates
Gemfile.lock
A package you depend on has a known security hole (CVE-2026-35611). Fix: Update that package to its patched version.
Worth fixing CVE-2018-1000201 ruby-ffi DDL loading issue on Windows OS
Gemfile.lock
A package you depend on has a known security hole (CVE-2018-1000201). Fix: Update that package to its patched version.
Worth fixing CVE-2018-17567 Jekyll through 3.6.2, 3.7.x through 3.7.3, and 3.8.x through 3.8.3 all ...
Gemfile.lock
A package you depend on has a known security hole (CVE-2018-17567). Fix: Update that package to its patched version.
via Trivy v0.70.0 · Apache-2.0
🧬 Known OSS vulnerabilities — OSV-Scanner ⓘ
5 found · 1 serious
Your dependencies cross-checked against the OSV vulnerability database.
Serious GHSA-mqm2-cgpr-p4m6 Unintended read access in kramdown gem
/workdirs/scan-84538140-0313-49e0-b282-53ceac21c0d5/Gemfile.lock
A package you depend on has a known security hole (CVE-2020-14001). Fix: Update that package to its patched version.
Worth fixing GHSA-h27x-rffw-24p4 Addressable has a Regular Expression Denial of Service in Addressable templates
/workdirs/scan-84538140-0313-49e0-b282-53ceac21c0d5/Gemfile.lock
A package you depend on has a known security hole (CVE-2026-35611). Fix: Update that package to its patched version.
Worth fixing GHSA-jxhc-q857-3j6g Regular Expression Denial of Service in Addressable templates
/workdirs/scan-84538140-0313-49e0-b282-53ceac21c0d5/Gemfile.lock
A package you depend on has a known security hole (CVE-2021-32740). Fix: Update that package to its patched version.
Worth fixing GHSA-2gw2-8q9w-cw8p Ruby-ffi has a DLL loading issue
/workdirs/scan-84538140-0313-49e0-b282-53ceac21c0d5/Gemfile.lock
A package you depend on has a known security hole (CVE-2018-1000201). Fix: Update that package to its patched version.
Worth fixing GHSA-4xjh-m3qx-49wc Jekyll allows attackers to access arbitrary files by specifying a symlink
/workdirs/scan-84538140-0313-49e0-b282-53ceac21c0d5/Gemfile.lock
A package you depend on has a known security hole (CVE-2018-17567). 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.