TypeScript · Next.js · Payments · Crown jewels
Last commit today by Kelvin · scanned today at 08:53 · 5 open, 3 critical
payments-api · src/config/aws.ts:14 · confirmed working
Chidi’s pull request on chidi/settlement-backfill was blocked, so it never reached main. But the commit is on GitHub, and we checked: the key still works. Deactivate it in AWS before anything else; deleting the line doesn’t take it back.
What it is, and where it goes
41 contributors · 1,284 files · a full scan every sunday at 03:00, and every push to main
12 weeks agoThis week · 17
Where it deploys
What's wrong in the code
5 open · secrets in the history, dependencies against advisories, our own rules for code flaws and infrastructure
Secrets · 1
Code flaws · 2
Dependencies · 2
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.