github.com/zotero/structured-document-text ↗

zotero/structured-document-text

scanned 2026-08-15 · git 387b726

1 of 6 checks flagged a security issue

🟡 Worth a look

Only 4 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 vulnerabilities7Risky code patterns✓Malicious dependencies✓Project 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 120s

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

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumption

/workdirs/scan-c9711b6b-6885-4182-942a-928aa0f60d27/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-c9711b6b-6885-4182-942a-928aa0f60d27/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-c9711b6b-6885-4182-942a-928aa0f60d27/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-f23m-r3pf-42rh lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`

/workdirs/scan-c9711b6b-6885-4182-942a-928aa0f60d27/package-lock.json

A package you depend on has a known security hole (CVE-2025-13465). Fix: Update that package to its patched version.
Worth fixing GHSA-r5fr-rjxr-66jc lodash vulnerable to Code Injection via `_.template` imports key names

/workdirs/scan-c9711b6b-6885-4182-942a-928aa0f60d27/package-lock.json

A package you depend on has a known security hole (CVE-2021-23337). 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-c9711b6b-6885-4182-942a-928aa0f60d27/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-c9711b6b-6885-4182-942a-928aa0f60d27/package-lock.json

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