Security defaults that belong in every Spring Boot application from day one.
88
83%
Does it follow best practices?
Impact
97%
1.79xAverage score across 5 eval scenarios
Passed
No known issues
A development team needs a REST API for their task tracking tool. The API is built with Spring Boot and Java. A React frontend on a separate domain will consume it.
The API needs the following endpoints:
GET /api/tasks -- list all tasks (supports ?status=open&assignee=john query filters)GET /api/tasks/{id} -- get a single taskPOST /api/tasks -- create a new task (accepts title, description, priority HIGH/MEDIUM/LOW, assignee)PATCH /api/tasks/{id} -- update a task (change status, reassign, edit details)DELETE /api/tasks/{id} -- delete a taskPOST /api/tasks/{id}/comments -- add a comment to a task (accepts author, text)Use an in-memory data store. Tasks should have id, title, description, status (OPEN, IN_PROGRESS, DONE), priority, assignee, comments, and createdAt fields.
Produce:
TaskController.java -- REST controller with all endpointsTask.java -- Task modelCreateTaskRequest.java -- Request DTO for task creationSecurityConfig.java -- Security configurationpom.xml -- With all required dependenciesevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-security-basics
verifiers