jkone27/FsharpWebApi

This system is a legacy codebase primarily maintained through routine dependency updates and targeted fixes to its FSharpGiraffe web framework integration. It currently lacks defined deployable containers or bounded contexts, suggesting a simpler or monolithic architectural structure. Recent activity indicates a focus on stability and maintenance rather than new feature development or significant architectural shifts.

2 changes.

This period focused primarily on maintaining the project's external dependencies, with 18 commits dedicated to updating six manifests. Additionally, significant effort was directed toward behavioral changes within the FSharpGiraffe component, involving 36 commits that included four specific fixes. The work reflects a balance of routine maintenance and targeted improvements to the web framework integration.

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

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

• Code Health 53 → 53 (+0.0)
• Architecture 92 → 94 (+1.9)
• Maturity 51 → 51 (+0.0)
• Readiness 16 → 16 (+0.0)
• Security 48 → 48 (-0.4)

• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Inconsistent casing convention for properties in the CSharp.Contract namespace. Properties in PetDto and Category/Tag use lowercase (camelCase) for simple identifiers (id, name, status), while other properties in the same codebase (e.g., PersonDto.Id, Person.Id) use PascalCase. This creates a mixed casing style within the same contract layer.
• Typo in method name: 'GetPetsAync' is misspelled (missing 's' in Async). This is a distinct inconsistency from the correct 'GetPersonByIdAsync' and 'GetPersonsByName' methods.
• While both are named 'Id', the inconsistency lies in the parallel structure with the 'CSharp.Contract.PetDto' which uses 'id'. However, within the CSharpWebApiSample namespace, the naming is consistent. The primary issue is the cross-namespace inconsistency between CSharp.Contract and CSharpWebApiSample.Contracts regarding casing (see first finding).

• Inconsistent casing convention for properties in the CSharp.Contract namespace. Some properties use lowercase (id, name, status) while others use camelCase (photoUrls, category, tags). This suggests a mix of JSON serialization conventions or manual naming errors within the same DTO/Contract types.
• Inconsistent naming for the 'Name' property across different contracts and domain models. While CSharpWebApiSample uses PascalCase (Name), the CSharp.Contract namespace uses lowercase (name). This indicates a lack of standardization between the internal domain/contract layers and the external API contracts.
• Typo in method name: 'GetPetsAync' is missing the 's' in 'Async'. This is inconsistent with other async methods in the codebase which correctly use the 'Async' suffix (e.g., GetPersonByIdAsync, StartAsync, StopAsync).

• Unchanged — 5 HTTP endpoints

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

jkone27/FsharpWebApi 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.