Repository health

YpCIIIaK/repo-janitor

Scanned 3 Nov 2026 · 0 days old

D

52/100

Worse than 65% of repositories this sizeout of 37 scans

63 findings

4 critical2 warning57 info

  • dependency27
  • security18
  • hygiene15
  • env2
  • dead code1
  • ●next@16.3.8 has a known vulnerability (CVE-2026-94482)
  • ●next@16.3.8 has a known vulnerability (GHSA-2464-fhr4-w9xw)
  • ●next@16.3.8 has a known vulnerability (GHSA-673q-mjm6-r5xr)
  • ●zod@4.4.3 has a known vulnerability (CVE-2023-54404)
  • ●REPO_ANTI_ROT_OFFLINE used but not in .env.example
  • ●sharp@0.35.4 has a known vulnerability (CVE-2026-114111)
  • ●13 lines duplicated between two files
  • ●8 lines duplicated between two files
  • ●8 lines duplicated between two files
  • ●8 lines duplicated between two files

This is a shared summary: code evidence and secret values are not included.

TypeScript 62,483 · JavaScript 801
Project essentials5/9›
  • ✓ CI pipeline
  • ✓ Tests
  • ✓ README
  • ✓ License
  • ○ Security policy
  • ○ Changelog
  • ✓ .gitignore
  • ○ Contributing guide
  • ○ Code of conduct
Activity, last 12 months›

201 commits · 3 authors · 1 make 80% of commits

Watch for drops

Checking sign-in…

See it as it is today

Run the same scan yourself against the current code. Nothing is stored unless you ask for a link.

Scan YpCIIIaK/repo-janitor nowChecking whether the repository is still public…
Scan another repository