gitsafehub
github.com/elie222/pdf-generator ↗

elie222/pdf-generator

scanned 2026-08-05 · git fc8f834
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 dependencies5Known OSS vulnerabilities5Risky 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ⓘ 5 found · 2 serious

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

  • Serious CVE-2023-46233 crypto-js: PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
    yarn.lock
    A package you depend on has a known security hole (CVE-2023-46233). Fix: Update that package to its patched version.
  • Serious CVE-2021-44906 minimist: prototype pollution
    yarn.lock
    A package you depend on has a known security hole (CVE-2021-44906). Fix: Update that package to its patched version.
  • Worth fixing GHSA-6chw-6frg-f759 Regular Expression Denial of Service in Acorn
    yarn.lock
    A package you depend on has a known security hole (GHSA-6chw-6frg-f759). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-7598 nodejs-minimist: prototype pollution allows adding or modifying properties of Object.prototype using a constructor or __proto__ payload
    yarn.lock
    A package you depend on has a known security hole (CVE-2020-7598). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-23343 nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe
    yarn.lock
    A package you depend on has a known security hole (CVE-2021-23343). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 5 found · 2 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-xwcq-pm8m-c4vf crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
    /workdirs/scan-61b9bda6-9101-49b8-b244-458bde3db419/yarn.lock
    A package you depend on has a known security hole (CVE-2023-46233). Fix: Update that package to its patched version.
  • Serious GHSA-xvch-5gv4-984h Prototype Pollution in minimist
    /workdirs/scan-61b9bda6-9101-49b8-b244-458bde3db419/yarn.lock
    A package you depend on has a known security hole (CVE-2021-44906). Fix: Update that package to its patched version.
  • Worth fixing GHSA-6chw-6frg-f759 Regular Expression Denial of Service in Acorn
    /workdirs/scan-61b9bda6-9101-49b8-b244-458bde3db419/yarn.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-vh95-rmgr-6w4m Prototype Pollution in minimist
    /workdirs/scan-61b9bda6-9101-49b8-b244-458bde3db419/yarn.lock
    A package you depend on has a known security hole (CVE-2020-7598). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hj48-42vr-x3v9 Regular Expression Denial of Service in path-parse
    /workdirs/scan-61b9bda6-9101-49b8-b244-458bde3db419/yarn.lock
    A package you depend on has a known security hole (CVE-2021-23343). 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.