gitsafehub
github.com/opensumi/prompt-engine ↗

opensumi/prompt-engine

scanned 2026-08-12 · git 899733e
3 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 dependencies8Known OSS vulnerabilities7Risky code patternsMalicious dependencies1Project 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 8 found

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

  • Worth fixing CVE-2025-27789 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups
    yarn.lock
    A package you depend on has a known security hole (CVE-2025-27789). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-54803 js-toml Prototype Pollution Vulnerability
    yarn.lock
    A package you depend on has a known security hole (CVE-2025-54803). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-49293 js-toml vulnerable to CPU exhaustion via O(n^2) BigInt construction on radix-prefixed integer literals
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-49293). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50029 js-toml has silent type confusion via falsy-primitive duplicate-key bypass
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-50029). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-4800 lodash: lodash: Arbitrary code execution via untrusted input in template imports
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-4800). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-13465 lodash: prototype pollution in _.unset and _.omit functions
    yarn.lock
    A package you depend on has a known security hole (CVE-2025-13465). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-2950 lodash: Lodash: Prototype pollution allows deletion of built-in prototype properties via array path bypass
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-2950). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-33532 yaml: yaml: Denial of Service via deeply nested YAML document parsing
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-33532). Fix: Update that package to its patched version.

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-968p-4wvh-cqc8 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups
    /workdirs/scan-af4449b5-98a0-4261-a09f-77e2be7e08fe/yarn.lock
    A package you depend on has a known security hole (CVE-2025-27789). Fix: Update that package to its patched version.
  • Worth fixing GHSA-65fc-cr5f-v7r2 js-toml Prototype Pollution Vulnerability
    /workdirs/scan-af4449b5-98a0-4261-a09f-77e2be7e08fe/yarn.lock
    A package you depend on has a known security hole (CVE-2025-54803). Fix: Update that package to its patched version.
  • Worth fixing GHSA-m34p-749j-x6m6 js-toml has silent type confusion via falsy-primitive duplicate-key bypass
    /workdirs/scan-af4449b5-98a0-4261-a09f-77e2be7e08fe/yarn.lock
    A package you depend on has a known security hole (CVE-2026-50029). Fix: Update that package to its patched version.
  • Worth fixing GHSA-wp3c-266w-4qfq js-toml vulnerable to CPU exhaustion via O(n^2) BigInt construction on radix-prefixed integer literals
    /workdirs/scan-af4449b5-98a0-4261-a09f-77e2be7e08fe/yarn.lock
    A package you depend on has a known security hole (CVE-2026-49293). 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-af4449b5-98a0-4261-a09f-77e2be7e08fe/yarn.lock
    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-af4449b5-98a0-4261-a09f-77e2be7e08fe/yarn.lock
    A package you depend on has a known security hole (CVE-2021-23337). Fix: Update that package to its patched version.
  • Worth fixing GHSA-48c2-rrv3-qjmp yaml is vulnerable to Stack Overflow via deeply nested YAML collections
    /workdirs/scan-af4449b5-98a0-4261-a09f-77e2be7e08fe/yarn.lock
    A package you depend on has a known security hole (CVE-2026-33532). 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 1 found

Packages that look intentionally malicious: typosquats, sneaky install scripts.

  • Worth fixing guarddog-npm-npm-install-script npm-install-script match in dprint 0.45.1
    dprint
    A dependency shows signs of being intentionally malicious (typosquat, hidden install script, etc.). Fix: Don’t install it until you’ve verified the package. Consider removing it.

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.