mungell/add-email

scanned 2026-08-08 · git e70f935

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

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-22jq-vg5j-6vgg ip-address: misclassification of IPv4-mapped/NAT64 IPv6 addresses can bypass SSRF and trust-boundary checks

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole (CVE-2026-54272). Fix: Update that package to its patched version.
Worth fixing GHSA-4xrf-jv44-h6hh ip-address: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole (CVE-2026-69198). Fix: Update that package to its patched version.
Worth fixing GHSA-mwp4-54f8-5fhr ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole (CVE-2026-69192). Fix: Update that package to its patched version.
Worth fixing GHSA-28wg-ghj8-5hjv nanoid: non-secure generators can loop indefinitely with negative size

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole (CVE-2026-67214). Fix: Update that package to its patched version.
Worth fixing GHSA-2v37-7h3g-55p8 nanoid: custom generators can loop indefinitely when size is zero

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole (CVE-2026-67213). Fix: Update that package to its patched version.
Worth fixing GHSA-p6gq-j5cr-w38f Nodemailer: Message-level raw option bypasses disableFileAccess/disableUrlAccess, enabling arbitrary file read and full-response SSRF in the delivered message

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole. Fix: Update that package to its patched version.
Worth fixing GHSA-fxqj-rqcc-2cmp PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole (CVE-2026-69153). Fix: Update that package to its patched version.
Worth fixing GHSA-r28c-9q8g-f849 PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure

/workdirs/scan-90a95850-1f11-483a-b483-0b1f0ef1dc8e/pnpm-lock.yaml

A package you depend on has a known security hole. 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ⓘ 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.