bigtimebuddy/svg-reorient

scanned 2026-08-13 · git 9edb867

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 secrets✓Vulnerable dependencies4Known OSS vulnerabilities6Risky code patterns✓Malicious dependencies✓Project 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ⓘ 4 found

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

Worth fixing CVE-2024-4068 braces: fails to limit the number of characters it can handle

package-lock.json

A package you depend on has a known security hole (CVE-2024-4068). Fix: Update that package to its patched version.
Worth fixing CVE-2024-4067 micromatch: vulnerable to Regular Expression Denial of Service

package-lock.json

A package you depend on has a known security hole (CVE-2024-4067). Fix: Update that package to its patched version.
Worth fixing CVE-2026-33671 picomatch: Picomatch: Regular Expression Denial of Service via crafted extglob patterns

package-lock.json

A package you depend on has a known security hole (CVE-2026-33671). Fix: Update that package to its patched version.
Worth fixing CVE-2026-33672 picomatch: Picomatch: Data integrity compromised via method injection with crafted POSIX bracket expressions

package-lock.json

A package you depend on has a known security hole (CVE-2026-33672). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 6 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-grv7-fg5c-xmjg Uncontrolled resource consumption in braces

/workdirs/scan-69073c1c-6e0c-409e-99e6-67a2c28adef7/package-lock.json

A package you depend on has a known security hole (CVE-2024-4068). Fix: Update that package to its patched version.
Worth fixing GHSA-952p-6rrq-rcjv Regular Expression Denial of Service (ReDoS) in micromatch

/workdirs/scan-69073c1c-6e0c-409e-99e6-67a2c28adef7/package-lock.json

A package you depend on has a known security hole (CVE-2024-4067). Fix: Update that package to its patched version.
Worth fixing GHSA-3v7f-55p6-f55p Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching

/workdirs/scan-69073c1c-6e0c-409e-99e6-67a2c28adef7/package-lock.json

A package you depend on has a known security hole (CVE-2026-33672). Fix: Update that package to its patched version.
Worth fixing GHSA-c2c7-rcm5-vvqj Picomatch has a ReDoS vulnerability via extglob quantifiers

/workdirs/scan-69073c1c-6e0c-409e-99e6-67a2c28adef7/package-lock.json

A package you depend on has a known security hole (CVE-2026-33671). Fix: Update that package to its patched version.
Worth fixing GHSA-gcx4-mw62-g8wm DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS

/workdirs/scan-69073c1c-6e0c-409e-99e6-67a2c28adef7/package-lock.json

A package you depend on has a known security hole (CVE-2024-47068). Fix: Update that package to its patched version.
Worth fixing GHSA-mw96-cpmx-2vgc Rollup 4 has Arbitrary File Write via Path Traversal

/workdirs/scan-69073c1c-6e0c-409e-99e6-67a2c28adef7/package-lock.json

A package you depend on has a known security hole (CVE-2026-27606). 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.