williamkoller/clean-node-api

This system is an authentication service that manages user login flows, including email validation and token issuance. It provides a structured API for handling authentication requests, returning standardized HTTP responses and specific error codes for invalid credentials or server issues. The codebase is supported by a comprehensive testing and linting infrastructure to ensure code quality and reliability.

The repository was initialized with essential configuration files to support development workflows. This includes setting up Jest for unit and integration testing, configuring Husky and lint-staged for pre-commit and pre-push hooks, and establishing a Travis CI pipeline for continuous integration. Additionally, a jsconfig.json was added to support IDE navigation and linting, while a .gitignore file was created to exclude node\_modules and coverage directories.

(repo-wide) · high confidence

Users can now authenticate via the LoginRouter, which validates the email and password, calls the AuthUseCase, and returns an access token on success (200), a 401 for invalid credentials, or a 400/500 for validation or server errors. The change adds the LoginRouter, an HttpResponse helper for standardizing HTTP responses, and error classes (ServerError, UnauthorizedError, MissingParamError, InvalidParamError) to support this flow.

src/presentation · high confidence

Added tests for the AuthUseCase to verify that it throws a MissingParamError when the email or password parameters are missing.

src/domain · high confidence

The project now includes a complete development environment with Jest for testing, Standard for code linting, and Husky for Git hooks. The package.json defines scripts for running unit tests, CI coverage, and staged file checks, while dev dependencies include coveralls, lint-staged, and git-commit-msg-linter to enforce quality standards.

(dependencies) · high confidence

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

• CAI 54 → 55 (+0.4)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 70 → 70 (+0.0)
• Architecture 69 → 69 (+0.0)
• Maturity 46 → 49 (+2.8)
• Readiness 53 → 49 (-4.2)
• Security 75 → 80 (+5.0)

• Coverage not included — suite not readable by the collector
• Critical CVE: [GHSA redacted] (package-lock.json)
• Critical CVE: [GHSA redacted] (package-lock.json)
• Critical CVE: [GHSA redacted] (package-lock.json)
• Critical CVE: [GHSA redacted] (package-lock.json)
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• …and 33 more

• Critical CVE: [GHSA redacted] (package-lock.json)
• Critical CVE: [GHSA redacted] (package-lock.json)
• Critical CVE: [GHSA redacted] (package-lock.json)
• Critical CVE: [GHSA redacted] (package-lock.json)
• Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (the committed lockfile is in a format this engine cannot resolve)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• …and 29 more

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

williamkoller/clean-node-api 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.