Level-Up: Das sind die Jobboard und Stellenanzeigen Trends 2026
Alles in unserem Webinar am 15.04.2026, 10:00–11:00 Uhr
For Suxess Technology GmbH & Co. KG | May 2026
The job board platform operated by For Suxess Technology GmbH & Co. KG is built on a curated set of mature, widely adopted open-source components, integrated into a single Turborepo monorepo and de‐livered on Vercel’s European infrastructure. Every third-party package is governed by an automated, security-aware update pipeline that combines four controls: (i) a self-hosted Renovate bot running onGitHub-hosted runners under a dedicated GitHub App identity, (ii) a tiered minimum release-age policy of 7, 14, and 21 days depending on the type and impact of the update, (iii) continuous vulnerability scanning against the Open Source Vulnerabilities (OSV) database on every pull request and on a weekly schedule against the main branch, and (iv) mandatory human review with required status checks before any dependency change reaches production.
This paper documents the composition of the platform, the rationale behind the chosen components, and the operational controls that protect the supply chain. It is intended as a reference for customer due-diligence reviews, procurement assessments, and information-security questionnaires.
Modern web applications are assembled from hundreds of third-party software components. The integrity of the resulting product depends not only on the quality of the application code written in-house, but also on the trustworthiness of every transitive dependency and on the discipline with which those dependencies are maintained over time.
This document describes how the job board platform addresses both dimensions:
The intended reader is a technical or commercial counterpart at a customer organisation who needs a structured, accurate picture of the platform’s foundations without consulting source code.
The platform is organised as a pnpm workspace orchestrated by Turborepo, providing a singlesource of truth for all customer-facing applications and the shared libraries that support them.
LAYER | CONTENTS |
Applications | A primary job board and a set of customer-specific variants, each deployed as an independent application sharing a common code base |
Sharedpackages | Design system, AI integration helpers, observability, distributed rate limiting, shared TypeScript and Vitest configuration |
Tooling | Turborepo, Biome / Ultracite, Lefthook, syncpack, Vitest, Playwright |
All applications share a coherent, contemporary runtime stack:
Each dependency is selected against four criteria, in order: maturity and community (active main‐tainers, timely security releases, broad ecosystem adoption); provenance (preference for packages published by recognised organisations — Vercel, the React team, Radix UI, TanStack, MongoDB Inc.,Sentry, Upstash and similar — over individual maintainers); scope (the smallest dependency that solves the problem, to limit the supply-chain surface); and security posture (a public vulnerability-disclosure process, SemVer discipline, and a clean OSV history).
Versions shown below reflect the current target versions either in production or staged for the next merge wave by the automated update pipeline. The platform is consistently kept on the most recent stable release of each component compatible with the overall stack. A full alphabetised inventory of all direct dependencies is provided in Appendix A.
COMPONENT | VERSION | ROLE |
Turborepo | ^2.5.5 | Monorepo build orchestrator, incremental task graph |
pnpm | 10.33.4 | Deterministic package manager with content-addressable store |
Biome (via Ultracite) | 1.9.4 / 4.2.1 | Single-binary linter and formatter |
TypeScript | ^5.8.3 | Static type system |
Vitest | 3.2.4 | Unit and integration test runner |
Playwright | ^1.60.0 | End-to-end browser testing |
Lefthook | ^1.10.10 | Local Git hook manager (pre-push lint and typecheck) |
syncpack | ^14.3.1 | Cross-workspace dependency version normalisation |
tsx | ^4.21.0 | TypeScript script execution for tooling |
COMPONENT | VERSION | ROLE |
Next.js | 16.2.6 | React-based application framework, App Router |
React, React DOM | ^19.1.2 | UI runtime, with React Compiler enabled |
TailwindCSS | ^4.3.0 | Utility-first CSS system |
Radix UI | various (latest stable) | Unstyled, accessible UI primitives (dialog, select, popover, accordion, tooltip, etc.) |
Lucide React | ^0.577.0 | Icon set |
Framer Motion | ^12.38.0 | Animation library |
TanStack Query, Table | latest stable | Server-state synchronisation and data-grid rendering |
react-hook-form | ^7.74.0 | Form state and validation |
Zod | 4.3.6 | Runtime schema validation for all external inputs |
nuqs | 2.8.9 | Type-safe URL state |
Tiptap | ^3.22.5 | Rich-text editing |
dnd-kit | ^6.3.1 | Drag-and-drop |
Embla Carousel | ^8.6.0 | Carousel primitives |
React Email | ^6.0.8 | Transactional email templating |
React Day Picker | ^9.14.0 | Date picker |
Recharts | 3.8.1 | Charting (statistics surfaces) |
COMPONENT | VERSION | ROLE |
MongoDB Node Driver | ^6.13.0 | Primary database client |
Typesense | 3.0.6 | Search engine client |
pg | ^8.20.0 | PostgreSQL client (selected reporting paths) |
COMPONENT | VERSION | ROLE |
Better-Auth | 1.6.9 | Authentication framework |
jsonwebtoken | ^9.0.3 | JWT signing and verification |
Resend | ^6.12.2 | Primary transactional email |
@aws-sdk/client-ses | ^3.1038.0 | Amazon SES fallback path |
nodemailer | ^8.0.0 | SMTP delivery (where required by the customer) |
google-auth-library, googleapis | ^10.6.2 / ^155.0.1 | Google Workspace integration |
COMPONENT | VERSION | ROLE |
@sentry/nextjs | ^9.47.1 | Error tracking |
@upstash/ratelimit | ^2.0.5 | Distributed rate limiting (Redis) |
@upstash/redis | ^1.38.0 | Serverless Redis client |
@vercel/functions, @vercel/blob, @vercel/edge-config | ^2.2.8, ^2.3.1,^1.4.0 | Vercel platform integrations |
OSV-Scanner | v2.3.8 | Vulnerability scanning (CI) |
Renovate (self-hosted) | v46.1.14 | Automated dependency updatebot |
The platform’s dependencies are kept current by a fully automated, self-hosted pipeline. The design objective is to reconcile two requirements that are usually in tension: timely adoption of security fixes on the one hand, and protection against compromised or accidentally broken upstream releases on the other.
Updates are proposed by Renovate, a mature, open-source dependency-update bot, run on GitHub-hosted runners under a dedicated GitHub App identity installed exclusively on the job board repository. The App authenticates with a short-lived token generated from a private key held as a repository secret; no personal access tokens or human credentials are involved in the update path.
Renovate runs every three hours. Routine updates are batched and opened only during the configured publication window (Monday morning, Europe/Berlin time zone). Vulnerability-driven updates bypass this schedule and are proposed as soon as Renovate’s three-hour cycle reaches them, ensuring same-day reaction to disclosed CVEs.
The single most effective control against compromised package releases is to allow newly published versions to mature in the public ecosystem before they enter the build. History shows that the great majority of supply-chain compromises (typo-squatted packages, hijacked maintainer accounts, malicious post-install scripts) are detected by the wider community within days of publication. By deferring adoption, the platform substitutes a brief, controlled delay for an unbounded risk.
The platform applies three levels of release-age delay, calibrated to the impact and reversibility of each class of update:
LEVEL | SCOPE | MINIMUM RELEASEAGE |
Level 1 | Development-only dependencies (build tools, type definitions, testharnesses) | 7 days |
Level2 | Runtime dependencies — minor and patch updates (production codepath) | 14 days |
Level3 | Major updates of any dependency (semantically breaking changes) | 21 days + manualapproval |
In addition, pre-1.0 packages (versions of the form 0.x.y) are held for 14 days regardless of category, reflecting the empirical observation that pre-stable releases break more frequently per increment.
Vulnerability-driven updates are exempt from the release-age delay. When a CVE affecting an installed package is published, Renovate opens a security update immediately, labelled security for prioritised review.
Updates that semantically move together — for example, react together with react-dom and the matching @types definitions, or all @radix-ui/* packages — are bundled into a single pull request.Grouping is configured for the following ecosystems:
React, Next.js, Radix UI, TanStack, Sentry, Vercel, AI SDK, MongoDB, Tiptap, dnd-kit, Upstash, Turf, Embla Carousel, React Email, Tailwind, Leaflet, the test stack, and the tooling stack (Biome, Turbo, TypeScript, etc.).
The effect is that a typical weekly update wave consists of approximately eight to fifteen pull requests rather than forty to sixty, while still preserving small, reviewable diffs per logical concern.
A deliberate design choice: no dependency update is merged automatically. Every pull request, however small, is reviewed and approved by a human engineer before it can be merged. Auto-merge would marginally reduce reviewer load but would also eliminate the last line of defence against a compromised release that slipped through the release-age window and the automated checks. The grouping and tiered delay controls described above keep the human review burden manageable without compromising the gate.
The end-to-end update pipeline consists of the following components, all hosted on infrastructure already used by the platform:
COMPONENT | LOCATION | FUNCTION |
Renovate workflow | GitHub Actions, repository-internal | Detects updates, opens pull requests |
Renovate GitHub App | Organisation-scoped | Short-lived authentication, scoped to one repository |
renovate.json5 | Repository root | Declarative configuration (ecosystem groups, schedule, release-age levels) |
osv-scanner.toml | Repository root | Tracks accepted / won’t-fix advisories with reason and review date |
OSV-Scanner (PR) | GitHub Actions | Fails pull requests that introduce new CVEs |
OSV-Scanner(scheduled) | GitHub Actions, Monday06:00 UTC | Re-scans main branch for newly disclosed CVEs |
syncpack | Local + CI | Enforces cross-workspace version consistency |
Lefthook | Developer workstations | Pre-push lint and typecheck |
The platform uses Google’s OSV-Scanner, an open-source vulnerability scanner that compares the locked dependency graph against the Open Source Vulnerabilities database maintained by Google, GitHub, the npm Security Working Group, the Python Software Foundation, and other ecosystem stewards.
Two scans run continuously:
When an advisory is reported, three outcomes are possible:
No suppression is silent; every entry in osv-scanner.toml is reviewed in pull request and version-controlled.
In addition to OSV-Scanner, the platform inherits the Vercel Firewall for traffic-layer protection(general bot and abuse mitigation, configurable rate limits), and applies a second, application-awarerate-limiting layer via Upstash Redis on selected expensive endpoints. Sentry receives runtime errorsand feeds anomaly detection.
Every change — whether human-authored or proposed by Renovate — passes through a uniform set of automated gates before it can be merged to main.
GATE | TOOL | WHAT IT CHECKS |
Lint | Biome /Ultracite | Style, dead code, common defects, accessibility hints |
Tests | Vitest | Unit and integration tests for the primary applications and the shared design system |
Dependency drift | syncpack | All workspaces use compatible versions of shared dependencies |
Vulnerability diff | OSV-Scanner | No new CVE introduced by the change |
Smoke tests | Playwright | Live homepage and API health probes against the actual Vercel preview deployment of each application |
Buildverification | Vercel | A preview deployment per application and tenant compiles successfully |
Before any change can be pushed to a remote branch, Lefthook runs turbo lint and turbo type‐check locally on the developer’s workstation. This shortens the feedback loop and reduces the number of pull requests that fail in CI for trivial reasons.
The main branch is protected. Merges require all required status checks to be green and at least one approving human review. Force-pushes and direct pushes to main are disallowed. The same protection applies to Renovate-authored pull requests; the bot has no merge privileges.
The platform runs on Vercel, which retains every prior production deployment as an immutable, instantly promotable artifact. In the event of a regression, rollback is a single click, independent of source-control state. A complementary git revert of the offending merge commit reestablishes a coherent codebase for the next forward change.
The application layer runs on Vercel, with build and serverless function execution pinned to European regions. Persistent data is held in MongoDB Atlas (European regions) and Upstash Redis (European regions for rate-limit state). Transactional email is delivered via Resend (with Amazon SES as a fallback path) and, for select customers, via SMTP through a customer-provided server.
Awareness of the regulatory landscape that applies to the platform — and of changes coming over the next two to three years — is part of the platform’s operating posture. The relevant frameworks are:
In parallel to the operated job board, For Suxess Technology GmbH & Co. KG develops a Skill Matcher product internally. The Skill Matcher is not yet released to the public and is not part of any customer-facing deployment. It is described here only for completeness, to make the boundary between the operated platform and the internal product explicit, and to identify the additional components that the Skill Matcher introduces into the dependency graph.
The Skill Matcher introduces the following additional components, which are kept under the same Renovate update pipeline and OSV scanning regime as the rest of the monorepo:
COMPONENT | VERSION | ROLE WITHIN THE INTERNAL PRODUCT |
Vercel AI SDK | latest stable | Provider-agnostic AI integration layer |
@ai-sdk/amazon-bedrock | latest stable | Amazon Bedrock provider for structured information extraction |
@xenova/transformers | ^2.17.2 | Local helper utilities |
@vercel/blob | ^2.3.1 | Short-lived storage for user-uploaded documents |
Upstash rate limiting | ^2.0.5 / ^1.38.0 | Per-endpoint rate limiting for AI-backed routes |
The job board platform combines a deliberately curated, modern open-source stack with a layered, mostly automated supply-chain control regime. The four-control model — release-age delay (7 / 14 /21 days), continuous OSV-based vulnerability scanning, automated quality gates, and mandatory human review — protects the platform against the most common classes of dependency-chain incident while keeping the operational overhead proportional to the size of a small engineering team.
Planned enhancements over the next twelve months include:
The platform is therefore well-positioned both for current customer expectations around information security and for the regulatory landscape emerging across the European Union over the next two to three years.
The following table lists every direct dependency declared across the monorepo, alphabetised, with theversion range either currently in production or staged for the next merge wave. Transitive dependenciesare managed via the pnpm lockfile (pnpm-lock.yaml) and are reviewed by OSV-Scanner on every pullrequest.
PACKAGE | VERSIONRANGE | PURPOSE |
@ai-sdk/amazon-bedrock | latest stable | Amazon Bedrock provider for the Vercel AI SDK (internal product, see§8) |
@aws-sdk/client-ses | ^3.1038.0 | Amazon SES transactional email |
@base-ui/react | ^1.4.1 | Headless UI primitives |
@dnd-kit/core, @dnd-kit/sortable | ^6.3.1 /^10.0.0 | Drag-and-drop primitives |
@formatjs/intl-localematcher | ^0.8.0 | Locale negotiation for i18n |
@hookform/resolvers | ^5.2.2 | Schema resolvers for react-hook-form |
@next/env | latest stable | Next.js environment loader |
@radix-ui/react-* | latest stable | Accessible, unstyled UI primitives |
@react-email/ui | ^6.0.8 | Email preview UI |
@react-leaflet/core | ^3.0.0 | Leaflet React bindings |
@sentry/nextjs | ^9.47.1 | Error tracking |
@t3-oss/env-core, @t3-oss/env-nextjs | ^0.13.11 | Type-safe environment variableloader |
@tailwindcss/postcss,@tailwindcss/typography | ^4.3.0 /^0.5.16 | TailwindCSS integrations |
@tanstack/react-query, @tanstack/react-query-devtools | latest stable | Server-state synchronisation |
@tanstack/react-table | latest stable | Headless data tables |
@testing-library/react, @testing-library/dom, @testing-library/user-event | ^16.3.0 /^10.4.0 /^14.6.1 | Testing library |
@tiptap/* (starter-kit, react, pm, extension-table-*, extension-placeholder) | ^3.22.5 | Rich-text editor |
@turf/circle, @turf/helpers | ^7.3.5 | Geospatial helpers |
@upstash/ratelimit, @upstash/redis | ^2.0.5 /^1.38.0 | Distributed rate limiting |
@vercel/blob, @vercel/edge-config,@vercel/functions | ^2.3.1 / ^1.4.0/ ^2.2.8 | Vercel platform integrations |
@xenova/transformers | ^2.17.2 | In-process embedding models(internal product, see §8) |
ai | latest stable | Vercel AI SDK (internal product, see§8) |
autoprefixer | ^10.4.18 | PostCSS plugin |
aws4 | ^1.13.2 | AWS SigV4 request signing |
babel-plugin-react-compiler | ^1.0.0 | React Compiler optimisation pass |
better-auth | 1.6.9 | Authentication framework |
chart.js, chartjs-plugin-datalabels,react-chartjs-2 | ^4.5.1 / ^2.2.0/ ^5.3.1 | Charting |
class-variance-authority | ^0.7.0 | Variant utilities for component APIs |
clsx | ^2.1.1 | Conditional class names |
cmdk | ^1.1.1 | Command-palette primitive |
date-fns, dayjs | ^4.1.0 /^1.11.20 | Date handling |
dotenv | ^17.4.2 | .env file loader for tooling |
embla-carousel-react, embla-carousel-autoplay | ^8.6.0 | Carousel |
form-data | ^4.0.4 | Multipart form bodies |
framer-motion | ^12.38.0 | Animation |
google-auth-library, googleapis | ^10.6.2 /^155.0.1 | Google Workspace integration |
html2canvas-pro | ^1.6.7 | Client-side rasterisation |
input-otp | ^1.4.2 | One-time password UI |
jsdom | ^26.1.0 | DOM for Vitest |
jsonwebtoken | ^9.0.3 | JWT signing and verification |
leaflet, leaflet.markercluster, react-leaflet | ^1.9.4 / ^1.5.3 /^5.0.0 | Maps |
lodash, lodash.debounce | ^4.17.21 /^4.0.8 | Utility functions |
lucide-react | ^0.577.0 | Icon set |
maplibre-gl | ^5.5.0 | Alternative map renderer |
mongodb | ^6.13.0 | MongoDB driver |
mongodb-memory-server | ^10.4.1 | In-memory MongoDB for tests |
nanoid | ^5.1.9 | Compact unique IDs |
negotiator | ^1.0.0 | HTTP content negotiation |
next | 16.2.6 | Next.js framework |
next-themes | ^0.4.6 | Theme switching |
nodemailer | ^8.0.0 | SMTP delivery (where required bythe customer) |
nuqs | 2.8.9 | Type-safe URL state |
openai | ^5.23.2 | Translation pipeline only |
pdf-lib | ^1.17.1 | PDF generation |
pg | ^8.20.0 | PostgreSQL client |
postcss | ^8.5.14 | CSS pipeline |
qrcode.react | ^4.2.0 | QR-code rendering |
react, react-dom | ^19.1.2 | UI runtime |
react-countup | ^6.5.3 | Animated counters |
react-day-picker | ^9.14.0 | Date picker |
react-email | ^6.0.8 | Email templating |
react-hook-form | ^7.74.0 | Form state |
react-player, react-select, react-youtube | ^2.16.0 /^5.10.0 /^10.1.0 | Embedded media and rich selects |
recharts | 3.8.1 | Charting (statistics surfaces) |
resend | ^6.12.2 | Transactional email |
server-only | ^0.0.1 | Compile-time server boundarymarker |
sonner | ^2.0.6 | Toast notifications |
tailwind-merge | ^2.5.2 | Tailwind class deduplication |
tailwindcss, tailwindcss-animate, tw-animate-css | ^4.3.0 / ^1.0.7/ ^1.3.7 | CSS framework |
tsx | ^4.21.0 | TypeScript script runner |
typescript | ^5.8.3 | TypeScript compiler |
typesense | 3.0.6 | Search engine client |
usehooks-ts | ^3.1.1 | Common React hook utilities |
vaul | ^1.1.2 | Drawer primitive |
vitest | 3.2.4 | Test runner |
xlsx | ^0.18.5 | Excel-format export |
zod | 4.3.6 | Runtime validation |
Type definitions are managed as a single Renovate group. The platform consumes the following @types/* packages, kept on the latest version published for each: @types/node, @types/react, @types/react-dom, @types/jsonwebtoken, @types/leaflet, @types/leaflet.markercluster,@types/lodash, @types/lodash.debounce, @types/negotiator, @types/pg, @types/geojson, @types/react-table.
PACKAGE | VERSION | ROLE |
@biomejs/biome | 1.9.4 | Lint and format engine |
@playwright/test | ^1.60.0 | End-to-end test framework |
lefthook | ^1.10.10 | Git hook manager |
syncpack | ^14.3.1 | Cross-workspace version control |
turbo | ^2.5.5 | Task orchestrator |
ultracite | 4.2.1 | Biome preset distribution |
TERM | DEFINITION |
CVE | Common Vulnerabilities and Exposures — a standardised public identifier for a known security defect. |
EU CRA | European Union Cyber Resilience Act, which sets baseline cyber-security obligations for digital products placed on the EU market. |
Monorepo | A single source-control repository containing multiple, independently buildable packages and applications. |
OSV | Open Source Vulnerabilities — a unified, machine-readable vulnerability database maintained by a coalition of ecosystem stewards. |
pnpm | A fast, content-addressable Node.js package manager that produces deterministicinstalls. |
Release age(minimum) | A policy that prevents a newly published package version from being adopted until a specified amount of time has elapsed since its publication. |
Renovate | An open-source bot that proposes dependency updates as pull requests. |
SBOM | Software Bill of Materials — a structured inventory of every component of a software product. |
SemVer | Semantic Versioning, the convention major.minor.patch used by most open-source libraries. |
Turborepo | A monorepo build system for JavaScript / TypeScript codebases. |
Vercel | The hosting platform on which the application layer and serverless functions run. |
Workspace(pnpm) | A package within the monorepo addressed via the workspace:* protocol. |
This document describes the state of the platform as of the date shown above. It is reviewed at least quarterly and updated as the architecture and the regulatory environment evolve.
Questions andf eedback are welcome at the address shared during the engagement.