wiringbits/scala-webapp-template
54.5
Weak · 7 November 2026
8k
lines of production code
Scala
primary language
4
measurements over time
What this system is
Features
Admin service implementation for user logs and user listing
The AdminService has been introduced to handle administrative requests for retrieving user logs and listing users. It leverages the Chimney library to automatically map repository entities to API response models (AdminGetUserLogs and AdminGetUsers), reducing boilerplate conversion code. This service acts as the backend logic layer, fetching data from the UserLogsRepository and UsersRepository and transforming it into the structured responses expected by the API.
server/src/main/scala/net/wiringbits/services · high confidence
Initial API endpoint definitions for authentication, user management, and administration
This change introduces the core API endpoint definitions for the application, establishing the contract for client interactions. It includes authentication routes for logging in, logging out, and retrieving the current user profile; user management endpoints for account creation, email verification, password reset, and profile updates; and administrative endpoints for listing users and viewing user logs. Additionally, it provides a health check endpoint and an environment configuration endpoint to expose necessary settings to the frontend. These definitions are built using sttp-tapir and include shared utilities for error handling, session management, and admin authentication.
lib/api/shared/src/main/scala/net/wiringbits/api/endpoints · high confidence
Initial Nginx and server deployment configuration
This change introduces the foundational infrastructure configuration for deploying the application. It adds Nginx templates to serve the web and admin interfaces, including SSL termination via Let's Encrypt, basic authentication for admin routes, and proxying for API and Swagger endpoints. It also includes the main Nginx configuration, MIME types, and a systemd service file to manage the application server process, alongside a development environment template for database and application secrets.
infra/config · high confidence
Initial build scripts for admin, server, and web components
Added shell scripts (build-admin.sh, build-server.sh, build-web.sh) to automate the build and packaging process for the admin, server, and web applications. These scripts handle environment variable configuration (such as API\_URL and SWAGGER\_API\_BASEPATH), invoke sbt to build the respective modules, and package the outputs into zip files within the apps directory.
infra/scripts · high confidence
Initial database schema for user management and background jobs
The application now includes its initial database schema, introducing tables for user accounts (users), activity tracking (user\_logs), and verification tokens (user\_tokens). It also establishes a system for handling asynchronous tasks via a background\_jobs table and a user\_notifications table to queue email delivery, providing the foundational data structures required for user registration, authentication, and background processing.
server/src/main/resources/evolutions · high confidence
Initial implementation of data access objects for core domain entities
This change introduces the foundational repository layer for the application, adding new DAOs to manage persistence for Users, User Logs, User Tokens, and Background Jobs. The implementation provides specific capabilities for user management (creation, lookup, name updates, verification, and password resets), token handling for authentication flows, logging of user activities, and a streaming interface to fetch and process pending background jobs from the database.
server/src/main/scala/net/wiringbits/repositories/daos · high confidence
Initial implementation of user and background job data models
This change introduces the core data models for the application's user management and background job systems. It adds \User\ and \UserLog\ models to handle user profiles, authentication credentials, and activity logging, alongside \UserToken\ and \UserTokenType\ to support email verification and password reset workflows. Additionally, \BackgroundJobData\ is added to define the structure for scheduled and executed background tasks, including their status, payload, and execution timestamps.
server/src/main/scala/net/wiringbits/repositories/models · high confidence
Initial release of the Wiringbits Scala/Scala.js web application template
This commit introduces the initial skeleton for a reusable web application template built with Scala, Scala.js, and React. It establishes the foundational configuration and tooling, including a \.gitignore\ for IDE and build artifacts, \.nvmrc\ and \.sdkmanrc\ to pin Node.js (v24) and Java (v25) versions, and \.scalafmt.conf\ to enforce Scala 3 code formatting. It also provides a \custom.webpack.config.js\ that patches OpenSSL compatibility issues for Node 18+ and configures a development proxy to forward API requests to a local server while handling cookie domains. The entry includes a \README.md\ documenting the template's features, such as user authentication, PostgreSQL integration, and CI workflows, along with demo links.
(repo-wide) · high confidence
Initial release of the Wiringbits web application template
This change introduces the complete frontend skeleton for the Wiringbits web application, built with Scala.js and React (via Slinky). It provides a fully functional single-page application featuring user authentication (sign-in, sign-up, email verification, password reset), a user profile management section (editing name and password), and a dashboard. The app includes a responsive Material UI-based layout with an app bar, footer, and routing, along with internationalization support and a landing page describing the template's features.
web/src/main · high confidence
Initial server configuration and routing skeleton
This change introduces the foundational configuration files for the Play Framework server, including application.conf, logback.xml, messages, and routes. It establishes the default settings for database connectivity (PostgreSQL), session management, CORS filtering, and logging, while defining the primary API routing entry point at the root path.
server/src/main/resources · high confidence
Initial server module wiring and configuration setup
The server application now initializes its core infrastructure through a new set of Guice modules in the \modules\ package. This includes \ConfigModule\ to load and log settings for email, AWS, ReCaptcha, Swagger, and background jobs; \ApisModule\ to dynamically select the email provider (AWS or local logging); \ExecutorsModule\ to configure the database execution context; \TasksModule\ to register the background jobs executor; \ClockModule\ to provide a UTC clock; and \ApisModule\ to wire up the email API. This establishes the foundational dependency injection structure required for the application's email, background task, and configuration capabilities.
server/src/main/scala/net/wiringbits/modules · high confidence
Introduction of dedicated configuration models for AWS, email, ReCaptcha, and user tokens
The server now includes a set of new configuration case classes in the \net.wiringbits.config\ package to structure environment-specific settings. These include \AWSConfig\ for AWS credentials and region, \EmailConfig\ for sender details and provider, \ReCaptchaConfig\ for security keys, \UserTokensConfig\ for managing expiration times and HMAC secrets for email verification and password resets, \BackgroundJobsExecutorConfig\ for job scheduling intervals, \SwaggerConfig\ for API documentation metadata, and \WebAppConfig\ for the application host. These models replace ad-hoc configuration access with typed, validated configuration objects, enabling better support for AWS integration, reCAPTCHA verification, and token-based security flows.
server/src/main/scala/net/wiringbits/config · high confidence
Introduction of email sending and reCAPTCHA verification APIs
This change introduces new API abstractions and implementations for email delivery and bot protection. The EmailApi trait and its AWS SES-based implementation (EmailApiAWSImpl) enable sending HTML and text emails via Amazon Simple Email Service, while a new ReCaptchaApi provides verification against Google's reCAPTCHA service. These components are supported by the new EmailRequest model, establishing the backend infrastructure for secure user registration and communication flows.
server/src/main/scala/net/wiringbits/apis · high confidence
Introduction of typed, validated input components
The UI library now includes a new \ValidatedTextInput\ component that integrates with the project's form field system to provide automatic validation for text inputs. This change introduces specific input components for Name, Email, and Password fields, which leverage the new \TextValidator\ mechanism to display validation errors and manage input state directly within the UI layer.
lib/ui · high confidence
New email verification and password reset infrastructure
The server now includes a complete utility layer to support email-based account verification and password recovery flows. This introduces an \EmailsHelper\ that generates HMAC-SHA1 signed tokens for security, sends verification and password-reset emails via the \EmailApi\, and manages token storage in the \UserTokensRepository\. Supporting this are new models and utilities: \EmailMessage\ defines the HTML content for registration, confirmation, and password reset emails (with HTML escaping for user data), \TokenGenerator\ creates unique identifiers, \TokensHelper\ handles the cryptographic signing and validation, \StringUtils\ provides data masking for logs, and \DelayGenerator\ offers retry delay calculations. This change enables the backend to securely issue and validate email tokens required for the new forgot/reset password and registration confirmation endpoints.
server/src/main/scala/net/wiringbits/util · high confidence
New validation components for user authentication and security
The server now includes dedicated validation components to enforce security and integrity checks during user operations. These include verifying reCAPTCHA responses, ensuring email availability or registration status, validating password matches using bcrypt, checking user verification status, and validating the expiration of user tokens. These components provide a consistent way to handle common authentication and user management validations across the application.
server/src/main/scala/net/wiringbits/validations · high confidence
User account management and background job infrastructure
This change introduces the core repository layer for user account lifecycle management and background job processing. Users can now have their accounts created, updated, and verified, with password reset capabilities that trigger asynchronous email notifications via a new background job system. The implementation includes dedicated repositories for managing user tokens (for email verification), user activity logs, and background jobs, all wired to a dedicated database execution context to ensure non-blocking database operations.
server/src/main/scala/net/wiringbits/repositories · high confidence
Behavioural changes
1 commit (0 fixes) modifying claude
A change to existing behaviour in claude — 1 commit, 5 files: “Add Orca review workflows for rule enforcement (\#449)” (refs \#449).
claude · medium confidence · unverified
1 commit (0 fixes) modifying docker
A change to existing behaviour in docker — 1 commit, 2 files: “Allow running the app with docker compose (\#453)” (refs \#453).
docker · medium confidence · unverified
2 commits (0 fixes) modifying server/src/main/scala/net/wiringbits/actions
A change to existing behaviour in server/src/main/scala/net/wiringbits/actions — 2 commits, 11 files: “Inject a PasswordHasher so Play specs run real bcrypt at a cheap cost (\#450)”; “Organize actions and api models (\#429)” (refs \#450, \#429).
server/src/main/scala/net/wiringbits/actions · medium confidence · unverified
4 commits (0 fixes) modifying server/src/main/scala/net/wiringbits/models
A change to existing behaviour in server/src/main/scala/net/wiringbits/models — 4 commits, 5 files: “Log masked secrets when the server starts (\#107)”; “Add endpoint to get environment properties (\#216)”; “Add ReCaptcha (\#104)”; and 1 more (refs \#107, \#216, \#104, \#111).
server/src/main/scala/net/wiringbits/models · medium confidence · unverified
4 commits (0 fixes) modifying server/src/main/scala/net/wiringbits/models/jobs
A change to existing behaviour in server/src/main/scala/net/wiringbits/models/jobs — 4 commits, 3 files: “Reformat code and organize imports in project (\#406)”; “Initial background jobs implementation (\#297)”; “Initial support for Scala 3 (\#380)”; and 1 more (refs \#406, \#297, \#380, \#452).
server/src/main/scala/net/wiringbits/models/jobs · medium confidence · unverified
API request and response models are split into dedicated files with Tapir schema support
The API models in the shared library have been reorganized so that each request and response type (such as Login, CreateUser, and AdminGetUsers) is defined in its own file. These models now include explicit Play JSON formats and Tapir Schema definitions, enabling automatic serialization and structured API documentation generation.
lib/api/shared/src/main/scala/net/wiringbits/api/models · high confidence
Initial release of Play/Pekko/Tapir-based API controllers
The server's controller layer has been rewritten from scratch to use Play Framework 3, Pekko, and Tapir, replacing the previous implementation. This change introduces new controllers (Admin, Auth, EnvironmentConfig, Health, Users) that expose endpoints for user management, authentication, and system health. Key behavioral updates include session management via Play cookies (handled by PlayTapirBridge), email masking in admin user logs, and a unified error handling strategy that returns generic ErrorResponse objects for failures. The ApiRouter now aggregates these new Tapir endpoints and integrates Swagger documentation.
server/src/main/scala/controllers · high confidence
Introduction of typed domain models for user input validation
The shared models library now includes strongly-typed wrappers for Captcha, Email, Name, Password, and UserToken. These new classes enforce specific validation rules at the model level: Captcha requires a non-empty string, Email is validated against a standard regex pattern, Name must be at least two characters long, Password requires a minimum length of eight characters, and UserToken is parsed from a UUID-based string format. This change shifts validation logic from generic strings to specific types, ensuring data integrity for user registration and authentication flows.
lib/common/shared/src/main/scala/net/wiringbits/common/models · high confidence
New API client with cookie-based session handling and date formatting utility
The API client library has been replaced with a new implementation that manages authentication state by persisting session cookies from login responses and automatically attaching them to subsequent requests, ensuring seamless user sessions for non-browser clients. This client exposes endpoints for user management (creation, verification, updates), authentication (login, logout, password reset), and administrative functions (user logs, user listing), along with environment configuration retrieval. Additionally, a new utility has been added to format date-time values into a localized string representation for display purposes.
lib/api/shared/src/main/scala/net/wiringbits/api · high confidence
New error message for unverified email addresses
A new error message constant has been added to the common library to inform users when their email address has not been verified, specifically suggesting they check their spam folder if the verification email is missing.
lib/common/shared/src/main/scala/net/wiringbits/common · high confidence
Fixes
3 commits (2 fixes) fixing scripts
A fix in scripts — 3 commits (2 fixs), 1 file.
scripts · medium confidence · unverified
Test coverage
Added controller integration tests for authentication, user management, and admin features; Added repository tests for background jobs, user logs, user tokens, and users; Added test infrastructure for API and database testing; Added test infrastructure for repository integration tests; Added test utility for secure random number generation; Added test utility helpers for execution contexts, login flows, and repository data creation; Added tests for HomePage rendering stability; Added tests for ReCaptcha API verification; Added tests for SecureRandom in lib/common/js; Added unit tests for DelayGenerator and TokensHelper utilities; Added unit tests for authentication and user management form data; Added validation tests for email, name, password, and user token models.
Dependencies
179 commits updating dependencies (6 manifests)
A dependency / build maintenance change in (dependencies) — 179 commits (4 fixs), 6 files.
(dependencies) · medium confidence · unverified
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.
Score
- CAI 61 → 54 (-7.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 76 → 75 (-0.6)
- Architecture 74 → 73 (-0.7)
- Maturity 60 → 79 (+19.4)
- Readiness 58 → 34 (-23.7)
- Security 66 → 67 (+1.7)
- Performance 100 → 100 (+0.0)
Resolved (31)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- Low CVE: [GHSA redacted] (lib/api/js/yarn.lock)
- Medium CVE: [GHSA redacted] (lib/api/js/yarn.lock)
- Medium CVE: [GHSA redacted] (lib/api/js/yarn.lock)
- Medium CVE: [GHSA redacted] (lib/api/js/yarn.lock)
- Off-boarding risk: anonymized user #1
- Outdated: com.beachape:enumeratum_3
- Outdated: com.google.inject:guice
- Outdated: com.softwaremill.sttp.tapir:tapir-json-play_3
- Outdated: com.softwaremill.sttp.tapir:tapir-play-server_3
- Outdated: com.softwaremill.sttp.tapir:tapir-sttp-client_3
- Outdated: com.softwaremill.sttp.tapir:tapir-swagger-ui-bundle_3
- Outdated: commons-validator:commons-validator
- Outdated: io.scalaland:chimney_3
- Outdated: org.apache.pekko:pekko-actor-typed_3
- Outdated: org.apache.pekko:pekko-actor_3
- Outdated: org.apache.pekko:pekko-serialization-jackson_3
- …and 11 more
New (87)
- Critical CVE: [GHSA redacted] (lib/common/js/yarn.lock)
- Critical CVE: [GHSA redacted] (lib/ui/yarn.lock)
- Critical CVE: [GHSA redacted] (web/yarn.lock)
- Critical CVE: [GHSA redacted] (lib/common/js/yarn.lock)
- Critical CVE: [GHSA redacted] (lib/ui/yarn.lock)
- Critical CVE: [GHSA redacted] (web/yarn.lock)
- Critical CVE: [GHSA redacted] (lib/common/js/yarn.lock)
- Critical CVE: [GHSA redacted] (lib/ui/yarn.lock)
- Critical CVE: [GHSA redacted] (web/yarn.lock)
- Dependency hygiene PARTLY measured — sbt declarations read, dependency currency not (Maven Central unreachable)
- High CVE: [GHSA redacted] (lib/common/js/yarn.lock)
- High CVE: [GHSA redacted] (lib/ui/yarn.lock)
- High CVE: [GHSA redacted] (web/yarn.lock)
- High CVE: [GHSA redacted] (lib/common/js/yarn.lock)
- High CVE: [GHSA redacted] (lib/api/js/yarn.lock)
- High CVE: [GHSA redacted] (lib/common/js/yarn.lock)
- High CVE: [GHSA redacted] (lib/ui/yarn.lock)
- High CVE: [GHSA redacted] (web/yarn.lock)
- High CVE: [GHSA redacted] (lib/common/js/yarn.lock)
- High CVE: [GHSA redacted] (web/yarn.lock)
- …and 67 more
Changes since last survey
- 8 commits — 8 feature/other, 0 fixes
By area
- server/src — 4 commits
- (root) — 2 commits
- .github/workflows — 1 commit
- .orca/reviewers — 1 commit
Notable commits
- change: Add Orca review workflows for rule enforcement (#449)
- change: Allow running the app with docker compose (#453)
- change: Inject a PasswordHasher so Play specs run real bcrypt at a cheap cost (#450)
- change: Run background jobs in independent per-type streams with an atomic claim (#452)
- change: Share one Postgres container across the server test suite + run in parallel (#451)
- change: Speed up CI: warm sbt server, caching, path-scoping, pinned actions (#448)
- change: Stop CI/orca builds from rewriting yarn.lock (--pure-lockfile) (#446)
- change: Use the application's ActorSystem in ApiRouter (drop the leaked one) (#447)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
wiringbits/scala-webapp-template was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 7 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit fc78f6eb6b5c5228938ceb459d8cdb8924f0189a — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-5f8314471808.