itchyny/s3-cache-action

scanned 2026-08-13 · git 9480eb7

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-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumption

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole (CVE-2026-59869). Fix: Update that package to its patched version.
Worth fixing GHSA-5p4m-2wfm-xmqj JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole. Fix: Update that package to its patched version.
Worth fixing GHSA-h67p-54hq-rp68 JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole (CVE-2026-53550). Fix: Update that package to its patched version.
Worth fixing GHSA-27v5-c462-wpq7 path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole (CVE-2026-4923). Fix: Update that package to its patched version.
Worth fixing GHSA-j3q9-mxjg-w52f path-to-regexp vulnerable to Denial of Service via sequential optional groups

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole (CVE-2026-4926). Fix: Update that package to its patched version.
Minor GHSA-4x5r-pxfx-6jf8 @babel/core: Arbitrary File Read via sourceMappingURL Comment

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole (CVE-2026-49356). Fix: Update that package to its patched version.
Minor GHSA-73rr-hh4g-fpgx jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole (CVE-2026-24001). Fix: Update that package to its patched version.
Minor GHSA-73rr-hh4g-fpgx jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch

/workdirs/scan-15fdfde5-d6a4-4fa0-b906-bc8e3d5f77d8/package-lock.json

A package you depend on has a known security hole (CVE-2026-24001). 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.