gitsafehub
github.com/hawkingrei/linkerdog_ppt ↗

hawkingrei/linkerdog_ppt

scanned 2026-08-07 · git 6d64382
2 of 6 checks flagged a security issue
🟡 Worth a look
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secretsVulnerable dependenciesKnown OSS vulnerabilities33Risky code patternsMalicious dependencies1Project health

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 33 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-39q2-94rc-95cp DOMPurify's ADD_TAGS function form bypasses FORBID_TAGS due to short-circuit evaluation
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65903). Fix: Update that package to its patched version.
  • Worth fixing GHSA-76mc-f452-cxcm DOMPurify: Hook mutation of `data.allowedTags` / `data.allowedAttributes` permanently pollutes `DEFAULT_ALLOWED_TAGS` / `DEFAULT_ALLOWED_ATTR`
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65902). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cj63-jhhr-wcxv DOMPurify USE_PROFILES prototype pollution allows event handlers
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65913). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cjmm-f4jc-qw8r DOMPurify ADD_ATTR predicate skips URI validation
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65912). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cmwh-pvxp-8882 DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65898). Fix: Update that package to its patched version.
  • Worth fixing GHSA-crv5-9vww-q3g8 DOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41239). Fix: Update that package to its patched version.
  • Worth fixing GHSA-h7mw-gpvr-xq4m DOMPurify: FORBID_TAGS bypassed by function-based ADD_TAGS predicate (asymmetry with FORBID_ATTR fix)
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41240). Fix: Update that package to its patched version.
  • Worth fixing GHSA-h8r8-wccr-v5f2 DOMPurify is vulnerable to mutation-XSS via Re-Contextualization
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65914). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hpcv-96wg-7vj8 DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checks
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49458). Fix: Update that package to its patched version.
  • Worth fixing GHSA-r47g-fvhr-h676 DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOM
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49459). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rp9w-3fw7-7cwq DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside <template>.content
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49978). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v2wj-7wpq-c8vv DOMPurify contains a Cross-site Scripting vulnerability
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-0540). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v9jr-rg53-9pgp DOMPurify: Prototype Pollution to XSS Bypass via CUSTOM_ELEMENT_HANDLING Fallback
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41238). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cmwh-pvxp-8882 DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65898). Fix: Update that package to its patched version.
  • Worth fixing GHSA-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumption
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59869). Fix: Update that package to its patched version.
  • Worth fixing GHSA-5p4m-2wfm-xmqj JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-h67p-54hq-rp68 JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-53550). Fix: Update that package to its patched version.
  • Worth fixing GHSA-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumption
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59869). Fix: Update that package to its patched version.
  • Worth fixing GHSA-5p4m-2wfm-xmqj JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-v245-v573-v5vm linkify-it: Quadratic-complexity DoS via the `mailto:` validator scan-loop on attacker text
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59887). Fix: Update that package to its patched version.
  • Worth fixing GHSA-2v8p-3f2j-5mp7 Mermaid XY Charts are vulnerable to an infinite loop DoS
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-71436). Fix: Update that package to its patched version.
  • Worth fixing GHSA-3rrr-jr9j-h3q3 Mermaid Architecture diagrams are vulnerable to prototype pollution
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-71437). Fix: Update that package to its patched version.
  • Worth fixing GHSA-6x64-9x62-f2gx Mermaid allows CSS injection applying to sibling elements of the diagram
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-50159). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rhh3-jpg6-66xh Mermaid radar diagrams are vulnerable to DoS
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-71439). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fxqj-rqcc-2cmp PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset
    /workdirs/scan-af9d23de-2c89-4b98-9bd6-bb75cc5a0c5e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-69153). Fix: Update that package to its patched version.
… 8 more not shown

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 1 found

Packages that look intentionally malicious: typosquats, sneaky install scripts.

  • Worth fixing guarddog-npm-npm-install-script npm-install-script match in playwright-chromium 1.62.1
    playwright-chromium
    A dependency shows signs of being intentionally malicious (typosquat, hidden install script, etc.). Fix: Don’t install it until you’ve verified the package. Consider removing it.

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.