gitsafehub
github.com/gregnr/transformers-edge-function-poc ↗

gregnr/transformers-edge-function-poc

scanned 2026-08-11 · git a50964b
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✓Known OSS vulnerabilities13Risky code patterns✓Malicious 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ⓘ 13 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-23hp-3jrh-7fpw node-tar: Decompression/parse DoS via unlimited input
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59873). Fix: Update that package to its patched version.
  • Worth fixing GHSA-34x7-hfp2-rc4v node-tar Vulnerable to Arbitrary File Creation/Overwrite via Hardlink Path Traversal
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-24842). Fix: Update that package to its patched version.
  • Worth fixing GHSA-83g3-92jg-28cx Arbitrary File Read/Write via Hardlink Target Escape Through Symlink Chain in node-tar Extraction
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-26960). Fix: Update that package to its patched version.
  • Worth fixing GHSA-8qq5-rm4j-mr97 node-tar is Vulnerable to Arbitrary File Overwrite and Symlink Poisoning via Insufficient Path Sanitization
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-23745). Fix: Update that package to its patched version.
  • Worth fixing GHSA-8x88-c5mf-7j5w node-tar: Negative tar entry size causes infinite loop in archive replace
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59874). Fix: Update that package to its patched version.
  • Worth fixing GHSA-9ppj-qmqm-q256 node-tar Symlink Path Traversal via Drive-Relative Linkpath
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-31802). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f5x3-32g6-xq36 Denial of service while parsing a tar file due to lack of folders count validation
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2024-28863). Fix: Update that package to its patched version.
  • Worth fixing GHSA-gvwx-54wh-qm9j node-tar: Uncaught Exception DoS via NUL byte in PAX path/linkpath records
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59875). Fix: Update that package to its patched version.
  • Worth fixing GHSA-qffp-2rhf-9h96 tar has Hardlink Path Traversal via Drive-Relative Linkpath
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-29786). Fix: Update that package to its patched version.
  • Worth fixing GHSA-r292-9mhp-454m node-tar: Uncontrolled recursion in mapHas/filesFilter allows uncatchable stack-overflow DoS via crafted long-path tar with member selection
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-r6q2-hw4h-h46w Race Condition in node-tar Path Reservations via Unicode Ligature Collisions on macOS APFS
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-23950). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vmf3-w455-68vh node-tar applies PAX size override to intermediary GNU long-name/long-link headers, causing tar parser interpretation differential (file smuggling)
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-53655). Fix: Update that package to its patched version.
  • Worth fixing GHSA-w8wr-v893-vjvp node-tar: Process crash via PAX numeric path type confusion
    /workdirs/scan-dde24c54-9583-4123-ac2d-4fa63f13ca4f/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59871). 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ⓘ 1 found

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

  • Worth fixing guarddog-npm-npm-install-script npm-install-script match in supabase 1.226.4
    supabase
    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.