gitsafehub
github.com/jayakumarpujar/work_with_my_agent ↗

jayakumarpujar/work_with_my_agent

scanned 2026-08-14 · git 62970c1
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets1Vulnerable dependencies15Known OSS vulnerabilities—Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ 1 found · 1 serious

API keys, passwords or tokens committed into the repo.

  • Serious gcp-api-key Uncovered a GCP API key, which could lead to unauthorized access to Google Cloud services and data breaches.
    .env.example:4
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 15 found

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

  • Worth fixing CVE-2026-67213 nanoid: nanoid: Denial of Service via infinite loop in random ID generation
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-67213). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-67214 nanoid (Nano ID) before 5.1.16 contains an infinite loop in the custom ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-67214). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64641 next: Next.js: Denial of Service via crafted requests to App Router with Server Actions
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64641). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64645 next: Next.js: Server-Side Request Forgery vulnerability
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64645). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64649 next: Next.js: Server-Side Request Forgery via malicious host redirection in Server Actions
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64649). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64643 next: Next.js: Information disclosure via Server Action ID exposure
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64643). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64644 next: Next.js: Denial of Service via malicious image optimization
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64644). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64646 next: Next.js: Denial of Service via excessive memory consumption in Server Actions
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64646). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64647 next: Next.js: Information disclosure via server-side request caching
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64647). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64648 next: Next.js: Information disclosure via server-side fetch cache
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64648). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-45623 postcss: PostCSS: Information disclosure and denial of service via crafted CSS input
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-45623). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-73646 PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-73646). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41305 postcss: PostCSS: Cross-Site Scripting (XSS) via improper escaping of style closing tags
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41305). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69153 postcss: PostCSS: Information disclosure via crafted sourceMappingURL
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-69153). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f88m-g3jw-g9cj sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591
    frontend/package-lock.json
    A package you depend on has a known security hole (GHSA-f88m-g3jw-g9cj). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 120s

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.