yezarela/go-lambda
64.1
Adequate · 21 September 2026
581
lines of production code
Go
primary language
4
measurements over time
What this system is
This system is a Go-based AWS Lambda application designed for user management, structured using clean architecture principles. It exposes RESTful endpoints via API Gateway to create new user accounts and retrieve paginated, sorted lists of existing users. The backend persists data to a MySQL database and includes infrastructure for local development and automated deployment.
Features
Initial project scaffolding for Go AWS Lambda application
This change introduces the foundational structure for a Go-based AWS Lambda project using the Serverless Application Model (SAM). It includes a Makefile to automate building, testing, and deploying Lambda functions (HelloWorld, UserList, UserCreate) via AWS SAM, along with a CloudFormation template defining the API Gateway, Lambda execution roles, and function resources. The setup also provides a local development environment via Docker Compose (MySQL 5.7), environment configuration files, and a .gitignore to manage build artifacts and dependencies.
(repo-wide) · high confidence
Introduction of domain models and interfaces for user management
The domain layer now defines the core data structures and contracts for user operations. This includes the User entity with ID, name, email, and timestamps, along with ListUserParams for query configuration. Standard error types (ErrNotFound, ErrConflict, ErrInvalidParameters) are established for consistent error handling. Additionally, UserRepository and UserUsecase interfaces are introduced to define the contract for user CRUD operations, supported by generated mocks to facilitate testing.
domain · high confidence
User management API with clean architecture and MySQL support
The application now exposes user management capabilities through AWS Lambda handlers, implementing a clean architecture pattern. Users can create new accounts via the user-create handler, which validates input (name, email) and persists data to a MySQL database, and retrieve paginated, sorted lists of users via the user-list handler. The infrastructure layer includes a new MySQL connection utility and standardized API response helpers for consistent error handling and status codes. Unit tests have been added for the Lambda handlers and repository layer to verify request processing and database interactions.
infra, user, utils · high confidence
Dependencies
Initial dependency setup for Go Lambda project
The project now includes a go.mod and go.sum file, establishing the initial set of dependencies required to build and run the application. This includes the AWS Lambda Go runtime, the MySQL driver, validation libraries, error handling utilities, and testing frameworks such as testify and go-sqlmock.
(dependencies) · high confidence
Written by watchdog.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 → 64 (+2.6)
- Rubric changed (rubric-2026.08.18 → rubric-2026.09.15) — scores are not directly comparable.
Lenses
- Code Health 100 → 100 (-0.3)
- Architecture 69 → 69 (+0.0)
- Maturity 61 → 61 (+0.0)
- Readiness 50 → 55 (+5.2)
- Security 88 → 91 (+3.1)
- Domain Modelling 100 → 100 (+0.0)
Resolved (11)
- Coverage not included — suite not readable by the collector
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- High: security finding (details withheld)
- High: security finding (details withheld)
- Medium CVE: GO-2021-0142 (go.mod)
- No exposed public API
- Test reliability not included
- early-stage repository — too little history to judge knowledge freshness
- git history depth insufficient
- git history depth insufficient
- single-maintainer — knowledge-concentration (bus factor) risk
New (22)
- Dependency pinned to a stale untagged commit: github.com/asaskevich/govalidator
- Documentation: no installation or build instructions (README.md)
- Documentation: no usage examples (README.md)
- Duplicated block (7 lines × 2) (user/handler/user-create/main.go)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- Low IaC: AWS-0125 (template.yaml)
- Low IaC: AWS-0125 (template.yaml)
- Medium CVE: GO-2021-0142 (go.mod)
- Medium IaC: WD-COMPOSE-0002 (docker-compose.yml)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- No ADRs found
- No dependency advisory monitoring
- Outdated: github.com/DATA-DOG/go-sqlmock
- Outdated: github.com/aws/aws-lambda-go
- Outdated: github.com/go-sql-driver/mysql
- Outdated: github.com/golang/mock
- Outdated: github.com/pkg/errors
- …and 2 more
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
yezarela/go-lambda 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 21 September 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 39cf38f0b89d3dc986854d42f103da799c48dab0 — the exact code this score is about.
- Scored under rubric-2026.09.15 — the same rubric and the same method as every other entry in this index.
- Measured by watchdog.canine.dev using codehealth-analyzer preprod-28e75b8e3254.