bbohec/bangarang

This is a web application built on the Svelte and Sapper framework, designed to manage claims and members through a server-side rendered interface. It exposes RESTful endpoints for claim and member interactions, utilizing Google Cloud Datastore as its primary data persistence layer while supporting a fake adapter for testing. The system includes comprehensive acceptance and integration tests to validate user registration, claim declaration, and data retrieval workflows.

New Svelte route files have been added to the \src/routes\ directory, implementing the frontend structure for the application's pages. This includes a root \index.svelte\ that redirects to the language-specific routes, and a set of \\[language\]/\ route files (such as \MainMenu\, \BusinessModel\, \Register\, \SignIn\, and \ClaimView\) that handle server-side data preloading and language context assignment. Additionally, specific pages for value propositions and landing pages have been introduced to support content-driven navigation.

src/routes · high confidence

The static/global.css file was added, importing Tailwind CSS v2.0.3 and modern-normalize v1.0.0, which applies a comprehensive set of utility classes and base styles to the application. Additionally, a new static/manifest.json file was created to define the web app manifest, specifying the app name, theme color, and icon assets.

static · high confidence

The client layer now includes a suite of new adapters that implement the application's interactor contracts. This includes a \RestInteractor\ for HTTP communication, alongside specific adapters for claims, members, and user interface states. The implementation provides both a production-ready \GcpDatastore\ adapter for Google Cloud Datastore and a \Fake\ adapter for testing or local development, allowing the client to interact with backend services through a consistent interface.

src/client · high confidence

The application has been migrated to use the Svelte framework and Sapper for server-side rendering, replacing the previous stack. The build system now utilizes Rollup with TypeScript support, and the styling is handled by Tailwind CSS, which is configured to purge unused styles in production builds. Configuration files for ESLint, TypeScript, PostCSS, and Vercel deployment have been added to support this new architecture.

(repo-wide) · high confidence

The application has been migrated to Sapper, introducing a new server entry point (src/server.ts) that handles API routes for claims and members, along with client-side initialization (src/client.ts) and a service worker for offline caching. The server now exposes REST endpoints for claim and member interactions, supporting both fake and GCP Datastore adapters. Additionally, Google Analytics tracking has been added to the HTML template.

src · high confidence

The Sapper build output has been regenerated, introducing a new build.json manifest that maps Svelte components (such as MainMenu, DeclareClaim, and Register) to their compiled JavaScript chunks. The server entry point (index.js) now explicitly sets the PORT environment variable to 3000 and requires the server module. The server.js bundle includes dependencies for Express, CORS, compression, and Google Cloud Datastore, while the service worker and template have been updated to reflect the new asset hashes and include Google Analytics tracking.

\\sapper\\_ · high confidence_

Added acceptance tests for user registration, claim declaration, and claim retrieval; Added integration tests for Bangarang claim and member interactors.

The project was initialized with a new set of dependencies, establishing the core technology stack. This includes Sapper (v0.28.10) and Svelte (v3.34.0) for the web framework, along with Tailwind CSS (v2.0.3) for styling. The configuration also adds essential build and development tools such as Rollup, TypeScript, Mocha for testing, and various Babel and PostCSS plugins. Additionally, production dependencies like Express, Axios, and Google Cloud Datastore are included to support the application's backend and data management needs.

(dependencies) · high confidence

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

• CAI 46 → 43 (-2.5)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 92 → 65 (-27.1)
• Architecture 99 → 86 (-12.5)
• Maturity 68 → 68 (+0.0)
• Readiness 31 → 30 (-1.1)
• Security 65 → 65 (+0.1)
• Accessibility 41 → 41 (+0.9)

• Boundary-crossing change coupling: FakeBangarangClaimInteractor.ts ↔ User.ts (src/client/adapters/FakeBangarangClaimInteractor.ts)
• Boundary-crossing change coupling: FakeBangarangMembersInteractor.ts ↔ User.ts (src/client/adapters/FakeBangarangMembersInteractor.ts)
• Boundary-crossing change coupling: User.ts ↔ BangarangClaimInteractorContract.ts (src/client/businessLogic/entities/User.ts)
• Change coupling: FakeBangarangClaimInteractor.ts ↔ FakeBangarangMembersInteractor.ts (src/client/adapters/FakeBangarangClaimInteractor.ts)
• 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)
• …and 42 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 68 more

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

bbohec/bangarang 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.