Auto-generated tile from GitHub (10 skills)
92
94%
Does it follow best practices?
Impact
92%
1.16xAverage score across 44 eval scenarios
Advisory
Suggest reviewing before use
The payments team at a growing fintech company is integrating with three external payment providers, each of which pushes JSON event notifications to a webhook endpoint. These notifications sometimes include sensitive fields such as authorization tokens and raw card metadata — the security team has mandated that those values must never appear in log files, which are shipped to a third-party SIEM provider.
The platform runs on Kubernetes, so the service must shut down cleanly when the pod is terminated: in-flight requests should be allowed to finish, the load balancer should stop routing new traffic before connections are drained, and database (or other) connections should be released in the correct order. The infrastructure team has asked for a health endpoint so the ingress controller can route traffic correctly during rolling deployments and pod restarts.
All code should be written in TypeScript and run directly under Node.js 22+ without a separate compilation step. The service does not need a real database or payment provider connection — stubs or in-memory representations are fine.
Deliver the following files:
src/server.ts — the main HTTP serversrc/logger.ts — logger setup and configurationpackage.json — with scripts to install dependencies and start the serverREADME.md — brief instructions covering how to install dependencies and run the serviceThe README should document any environment variables the service reads (e.g. port, log level). Do not include a .env file with real secrets.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
skills
documentation
fastify
init
linting-neostandard-eslint9
node
nodejs-core
rules
oauth
octocat
snipgrapher