gitsafehub
github.com/guybedford/chomp ↗

guybedford/chomp

scanned 2026-08-12 · git f6d78ba
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 secretsVulnerable dependencies11Known OSS vulnerabilities6Risky code patternsMalicious dependenciesProject 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 11 found

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

  • Worth fixing CVE-2026-42327 rust-openssl: rust-openssl: Arbitrary code execution via specially crafted certificate
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-42327). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-44662 rust-openssl provides OpenSSL bindings for the Rust programming langua ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-44662). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-45784 rust-openssl: rust-openssl: Heap Corruption from Incorrect Buffer Sizing
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-45784). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-21538 cross-spawn: regular expression denial of service
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2024-21538). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-21538 cross-spawn: regular expression denial of service
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2024-21538). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38900 decode-uri-component: improper input validation resulting in DoS
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2022-38900). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-33987 nodejs-got: missing verification of requested URLs allows redirects to UNIX sockets
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2022-33987). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-25881 http-cache-semantics: Regular Expression Denial of Service (ReDoS) vulnerability
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2022-25881). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-25883 nodejs-semver: Regular expression denial of service
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2022-25883). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-3795 semver-regex: inefficient regular expression complexity
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2021-3795). Fix: Update that package to its patched version.
  • Minor CVE-2021-43307 Regular expression denial of service in semver-regex
    node-chomp/package-lock.json
    A package you depend on has a known security hole (CVE-2021-43307). 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-phqj-4mhp-q6mq rust-openssl: Potential out-of-bounds write in `CipherCtxRef::cipher_update_inplace` for AES-KW-PAD ciphers
    /workdirs/scan-8b6ef2eb-0a64-4104-b4ba-e42b123b2b59/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-45784). Fix: Update that package to its patched version.
  • Worth fixing GHSA-xp3w-r5p5-63rr rust-openssl has undefined behavior in X509Ref::ocsp_responders for certificates with non-UTF-8 OCSP URLs
    /workdirs/scan-8b6ef2eb-0a64-4104-b4ba-e42b123b2b59/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-42327). Fix: Update that package to its patched version.
  • Worth fixing GHSA-xv59-967r-8726 rust-openssl vulnerable to heap buffer overflow when encrypting with AES key-wrap-with-padding
    /workdirs/scan-8b6ef2eb-0a64-4104-b4ba-e42b123b2b59/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-44662). Fix: Update that package to its patched version.
  • FYI RUSTSEC-2025-0056 adler crate is unmaintained, use adler2 instead
    /workdirs/scan-8b6ef2eb-0a64-4104-b4ba-e42b123b2b59/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0190 Unsoundness in `Error::downcast_mut()`
    /workdirs/scan-8b6ef2eb-0a64-4104-b4ba-e42b123b2b59/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0388 `derivative` is unmaintained; consider using an alternative
    /workdirs/scan-8b6ef2eb-0a64-4104-b4ba-e42b123b2b59/Cargo.lock
    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 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.