TypeScript · Next.js · Payments · Crown jewels
Last commit yesterday by Chidi · scanned yesterday at 17:20 · 2 open
web · apps/dashboard/src/app/sign-in/actions.ts:27 · seen on the web too
Sign-in sends people on to any address in ?next=. We see it in the code and on the live host, so it’s one issue with evidence from both sides. It closes only when the code rescan and the web retest both pass.
What it is, and where it goes
23 contributors · 2,210 files · a full scan every sunday at 03:00, and every push to main
12 weeks agoThis week · 12
Where it deploys
What's wrong in the code
2 open · secrets in the history, dependencies against advisories, our own rules for code flaws and infrastructure
Code flaws · 1
Dependencies · 1
How its pull requests are checked
Per repository · rules start in Monitor and move up once they prove quiet
What a check does
Blocks at
Comments, and new findings at or above the threshold stop the merge until they're fixed or someone approves ignoring them.
Only findings new in that pull request count. What’s already in main never blocks someone else’s change; it’s here, ranked, instead.
The next pull request can't merge if it adds a high or worse finding, until it's fixed or someone with approval rights waves it through.