React, React DOM, React Router
Single-page application UI, rendering, and routing.
This page lists the primary third-party software, frameworks, SDKs, infrastructure components, and external services intentionally integrated into Attriax. It is a practical notice page for direct dependencies and major runtime components, not an exhaustive dump of every transitive package.
Last updated: April 26, 2026
Attriax is built from multiple subproducts, including a React dashboard, a NestJS API, a Flutter SDK, deployment infrastructure, and connected third-party services. This page identifies the primary software components we intentionally include or rely on, along with the license family and an upstream reference.
Some listed packages bring their own transitive dependencies or platform-specific native components. Where those apply, the governing license remains the one distributed by the upstream project. If you self-host or redistribute Attriax in a materially different way, you should run your own dependency and legal review for that specific deployment.
Primary third-party libraries used to build and ship the Attriax dashboard and public site.
Single-page application UI, rendering, and routing.
Development server and production bundling for the frontend.
Source: https://vite.dev
Styling system and build integration.
Source: https://tailwindcss.com
Authentication flows and client identity integration.
HTTP requests, state management, charts, and iconography.
Source: https://github.com/axios/axios
lucide-react is ISC; Axios, Zustand, and Recharts are MIT.
Primary third-party libraries used to run the Attriax API, background work, security, uploads, and integrations.
Backend application framework and HTTP platform.
Source: https://github.com/nestjs/nest
Database persistence layer and PostgreSQL client.
Server-side Firebase token verification and user integration.
Security headers, uploads, Redis access, Telegram ops notifications, and image processing.
Source: https://helmetjs.github.io/
helmet, multer, ioredis, and node-telegram-bot-api are MIT; sharp is Apache-2.0.
GeoIP lookup support for analytics and fraud detection workflows.
Primary third-party packages used in the Flutter SDK, platform packages, and internal tester app.
SDK runtime, UI framework, and package tooling.
Source: https://flutter.dev
Connectivity status, device metadata, and package/app metadata collection.
Networking, local persistence, federated plugin contracts, and lint tooling.
Source: https://dart.dev
Icon assets and launcher icon generation for internal tooling.
Source: https://pub.dev
Primary third-party infrastructure components used in local and self-hosted deployments.
Primary relational datastore.
Source: https://www.postgresql.org
Caching and ephemeral data services in the compose stack.
Source: https://redis.io
The compose stack is pinned to the 7.2 line because later Redis 7 community releases use different source-available terms.
Reverse proxy, host routing, and TLS termination in self-hosted environments.
Source: https://nginx.org
Local development and deployment orchestration.
Source: https://www.docker.com
Some features rely on external providers that process account, payment, security, or geolocation-related information under their own terms and privacy policies. Those providers are part of the operational service, not just build-time dependencies.
Authentication, account identity, and related security workflows.
Firebase client and admin SDKs used in this repository are licensed under Apache-2.0.
Approximate IP geolocation data for analytics, fraud review, and geo reporting.
Attribution required: This product includes GeoLite Data created by MaxMind, available from https://www.maxmind.com. GeoLite data is also subject to the Creative Commons Attribution-ShareAlike 4.0 terms referenced in the GeoLite EULA.