referbruv/SwaggerHeroes

SwaggerHeroes is a .NET 6 ASP.NET Core web application that demonstrates API versioning and Swagger UI integration. It provides a layered architecture with a SQLite persistence layer for managing 'hero' entities, exposing both v1 and v2 API endpoints. The system features multi-version API documentation with Bearer token security and configuration-driven metadata.

The repository was initialized with a .NET 6 ASP.NET Core solution named SwaggerHeroes, which demonstrates integrating Swagger UI with API versioning. This update adds the foundational project files, including the solution file (SwaggerNinja.sln) defining the WebApi, Core, and Persistence projects, alongside a .gitignore configuration. Documentation is also established with a comprehensive README.md and an MIT LICENSE.md file.

(repo-wide) · high confidence

Added a new SQLite-based persistence implementation for the application. This includes a database context (HeroesContext) and an initial migration that creates the 'Heroes' table with columns for name, powers, cape status, creation date, alive status, and category. A generic Repository\<T\> base class and a concrete HeroesRepository are provided to handle data access, while a DataService class wires the repository to the context. The setup is registered via a ServiceExtensions method that configures the SQLite connection.

SwaggerHeroes.Persistence · high confidence

The WebApi project now exposes both v1 and v2 API controllers for managing heroes, enabling users to interact with the service through two distinct API versions. The v1 controller is marked as deprecated, while v2 introduces additional capabilities such as retrieving available categories. Additionally, the Swagger UI is configured to display API specification details (title, description, author, and website) sourced from the application's configuration file, providing better documentation for API consumers.

SwaggerHeroes.WebApi · high confidence

The application now configures Swagger UI to display API documentation for all discovered API versions, with each version presented as a separate endpoint in the UI. Additionally, Bearer token authentication is enabled in the Swagger UI, allowing users to authorize requests directly from the documentation interface. The API title, description, author, and website are now read from the application's configuration (appsettings) and displayed in the Swagger UI header.

SwaggerHeroes.Contracts · medium confidence

The project structure is updated to use .NET 6.0 across the core contracts, persistence, and WebApi layers. The persistence layer now references Microsoft.EntityFrameworkCore.Sqlite (v6.0.1) and related EF Core tools, enabling SQLite-based data access. The WebApi layer references the persistence and core projects, establishing a layered architecture that supports a DbContext with SQLite.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 49 → 49 (-0.0)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 92 → 89 (-3.4)
• Architecture 82 → 82 (+0.0)
• Maturity 51 → 51 (+0.0)
• Readiness 40 → 40 (+0.0)
• Security 46 → 47 (+0.4)

• High: security finding (details withheld)
• High: security finding (details withheld)
• No exposed public API
• early-stage repository — too few commits for a meaningful bus factor
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• git history depth insufficient
• redundant comment (SwaggerHeroes.Contracts/Options/ConfigureSwaggerOptions.cs)

• Documentation: no contributor guidance (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• End-of-life runtime: .NET net6.0
• High: security finding (details withheld)
• High: security finding (details withheld)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• No dependency advisory monitoring
• Workflow token permissions not restricted
• WriteOnlyPrivateField (SwaggerHeroes.WebApi/Controllers/V1/HeroesController.cs)
• WriteOnlyPrivateField (SwaggerHeroes.WebApi/Controllers/V2/HeroesController.cs)
• redundant comment (SwaggerHeroes.WebApi/Startup.cs)
• redundant comment (SwaggerHeroes.WebApi/Startup.cs)

• Unchanged — 2 HTTP endpoints

• Unchanged — 2 containers · 0 contexts · 0 edges

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

referbruv/SwaggerHeroes 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.