gitsafehub
github.com/tensorflow/tfjs-models ↗

tensorflow/tfjs-models

scanned 2026-06-29 · git c731b9e
1 of 6 checks flagged a security issue
🔴 Needs attention
Only 2 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secretsVulnerable dependencies174Known OSS vulnerabilitiesRisky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks timed out

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 v8.21.2 · MIT

error: timeout after 30s

Vulnerable dependencies — Trivy 174 found · 5 serious

Packages you depend on that have known security holes (CVEs).

  • Serious CVE-2025-7783 form-data: Unsafe random function in form-data
    speech-commands/training/soft-fft/yarn.lock
    A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
  • Serious CVE-2019-10744 nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying properties
    speech-commands/training/soft-fft/yarn.lock
    A package you depend on has a known security hole (CVE-2019-10744). Fix: Update that package to its patched version.
  • Serious CVE-2021-44906 minimist: prototype pollution
    speech-commands/training/soft-fft/yarn.lock
    A package you depend on has a known security hole (CVE-2021-44906). Fix: Update that package to its patched version.
  • Serious CVE-2025-7783 form-data: Unsafe random function in form-data
    speech-commands/yarn.lock
    A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
  • Serious CVE-2025-7783 form-data: Unsafe random function in form-data
    toxicity/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-26920 fast-xml-parser vulnerable to Prototype Pollution through tag or attribute name
    blazeface/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2023-26920). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41650 fast-xml-parser: fast-xml-parser: XML injection via improper escaping of comment and CDATA sequences
    blazeface/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2026-41650). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-0235 node-fetch: exposure of sensitive information to an unauthorized actor
    blazeface/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2022-0235). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-26920 fast-xml-parser vulnerable to Prototype Pollution through tag or attribute name
    body-pix/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2023-26920). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41650 fast-xml-parser: fast-xml-parser: XML injection via improper escaping of comment and CDATA sequences
    body-pix/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2026-41650). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-0235 node-fetch: exposure of sensitive information to an unauthorized actor
    body-pix/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2022-0235). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-26920 fast-xml-parser vulnerable to Prototype Pollution through tag or attribute name
    body-segmentation/demos/live_video/yarn.lock
    A package you depend on has a known security hole (CVE-2023-26920). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41650 fast-xml-parser: fast-xml-parser: XML injection via improper escaping of comment and CDATA sequences
    body-segmentation/demos/live_video/yarn.lock
    A package you depend on has a known security hole (CVE-2026-41650). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-28496 Denial of service in three
    body-segmentation/demos/live_video/yarn.lock
    A package you depend on has a known security hole (CVE-2020-28496). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-26920 fast-xml-parser vulnerable to Prototype Pollution through tag or attribute name
    body-segmentation/demos/upload_video/yarn.lock
    A package you depend on has a known security hole (CVE-2023-26920). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41650 fast-xml-parser: fast-xml-parser: XML injection via improper escaping of comment and CDATA sequences
    body-segmentation/demos/upload_video/yarn.lock
    A package you depend on has a known security hole (CVE-2026-41650). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-0235 node-fetch: exposure of sensitive information to an unauthorized actor
    body-segmentation/demos/upload_video/yarn.lock
    A package you depend on has a known security hole (CVE-2022-0235). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-33750 brace-expansion: brace-expansion: Denial of Service via zero step value in brace pattern
    body-segmentation/yarn.lock
    A package you depend on has a known security hole (CVE-2026-33750). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-3517 nodejs-minimatch: ReDoS via the braceExpand function
    body-segmentation/yarn.lock
    A package you depend on has a known security hole (CVE-2022-3517). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-26996 minimatch: minimatch: Denial of Service via specially crafted glob patterns
    body-segmentation/yarn.lock
    A package you depend on has a known security hole (CVE-2026-26996). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-27903 minimatch: minimatch: Denial of Service due to unbounded recursive backtracking via crafted glob patterns
    body-segmentation/yarn.lock
    A package you depend on has a known security hole (CVE-2026-27903). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-27904 minimatch: Minimatch: Denial of Service via catastrophic backtracking in glob expressions
    body-segmentation/yarn.lock
    A package you depend on has a known security hole (CVE-2026-27904). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-0235 node-fetch: exposure of sensitive information to an unauthorized actor
    coco-ssd/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2022-0235). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-0235 node-fetch: exposure of sensitive information to an unauthorized actor
    coco-ssd/yarn.lock
    A package you depend on has a known security hole (CVE-2022-0235). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-26920 fast-xml-parser vulnerable to Prototype Pollution through tag or attribute name
    deeplab/demo/yarn.lock
    A package you depend on has a known security hole (CVE-2023-26920). Fix: Update that package to its patched version.
… 149 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner timed out

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 v1.9.2 · Apache-2.0

error: timeout after 60s

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.