Chimpo
Log inSign up

Acknowledgements

This page lists third-party components and services used in or with Chimpo for transparency and attribution. It does not grant you any license beyond what each third party's own terms and licenses provide. Your use of third-party software remains subject to those licenses, applicable export and sanctions rules, and third-party terms of service. For the rules governing use of Chimpo itself, see our Terms of service and Privacy policy. If you distribute, modify, or build on Chimpo, you are responsible for your own license compliance and for any notices your use requires.

Open source software

Chimpo's applications and build tooling incorporate open-source and source-available packages. Each component is licensed under its own terms (for example MIT, Apache-2.0, ISC, BSD). Depending on how you use or distribute software, your obligations may include retaining copyright notices, providing license texts, documenting changes to copyleft-licensed code, or offering corresponding source for certain distribution models. Review the licenses that apply to your situation if you ship binaries or offer hosted services.

Representative packages used in the web client and tooling include, without limitation:

  • Next.js, React, React DOM — application framework and UI runtime.
  • TypeScript — static typing.
  • Tailwind CSS — styling.
  • Zod, React Hook Form, @hookform/resolvers — validation and forms.
  • Vitest, Testing Library, jsdom — tests.
  • ESLint, eslint-config-next — linting.
  • Sonner — toasts.
  • Lucide React — icons.
  • @livekit/components-react, livekit-client — real-time video (Apache-2.0 and related).
  • @supabase/ssr, @supabase/supabase-js — auth and data client.

Transitive dependencies are numerous. For production releases, maintain a full dependency and license inventory (for example via pnpm licenses list, SBOM tools, or your compliance workflow) and archive license files with release artifacts if your program requires it.

Disclaimer of warranties (third-party software)

Open-source and third-party components are provided under their respective licenses, often on an "as is" basis, without warranties of any kind, to the extent those licenses disclaim them. Contributors and copyright holders disclaim liability for damages arising from use of such software to the extent permitted by those licenses. Chimpo does not warrant that any third-party component is free of defects, vulnerabilities, or infringement claims. You should monitor security advisories and apply patches promptly.

Fonts

We may load Geist Sans and Geist Mono via next/font. Font files are subject to their own license terms; ensure your hosting and embedding model complies with those terms and with any font vendor requirements for your traffic and regions.

Infrastructure and subprocessors

Production deployments may use cloud hosting, databases, real-time media servers, DNS, TLS certificates, logging, error reporting, and analytics vendors. Each has its own terms, privacy policy, data processing terms, and regional options. Customers and operators are responsible for agreements, region configuration, and subprocessor listings required for their own compliance. We do not control third-party infrastructure outages, pricing changes, or deprecations.

Trademarks and names

Product and project names (for example framework and library names) are trademarks of their respective owners. Mention on this page is for identification only and does not imply sponsorship, endorsement, or affiliation. Do not use third-party marks in a way that suggests endorsement of your product without permission.

Patents and standards

Open-source licenses may include patent grants or defensive termination provisions. Video, networking, and cryptography stacks may implicate standards or codec licensing in some jurisdictions. If you ship hardware, distribute native app store builds, or operate at very large scale, consider patent and standards obligations that apply to your deployment. Nothing on this page grants you a patent license from Chimpo.

Export and encryption

Software may include cryptographic functionality. You are responsible for compliance with applicable export, import, and sanctions laws when distributing software or offering services across borders.

Updates

Dependency versions change over time. This page may not list every package at every revision. Automated license and vulnerability scanning should be part of your release process.

For personal data practices, see our Privacy policy. For use of the Services, see our Terms of service.