Skip to main content

Open Source

Dollaroodle depends on open source.

The product runs on frameworks, runtimes, libraries, databases, developer tools, and testing systems built in public.

This page thanks those projects and lists the direct packages we ship with today.

Current appendix snapshot

Direct packages

92

Package groups

5

License labels

5

The appendix comes from the repository lockfiles, so this page shows what Dollaroodle ships with today.

How we treat the dependency tree

We depend on maintainers

Every package is maintainer time, issue triage, documentation, releases, and bug fixes. This page is a thank-you.

We list what we ship

The appendix groups the direct Composer and npm packages Dollaroodle declares for runtime, development, testing, and build work.

We try to use them carefully

We prefer stable foundations, read licenses, test our changes, and keep our own code understandable.

Direct dependencies, grouped by declared use

This appendix lists direct dependencies from Composer and npm, including runtime packages, development tools, browser testing tools, and optional platform-specific build binaries.

For browser-delivered code, Dollaroodle also publishes a machine-generated license inventory with bundled license identifiers and embedded notice text where package metadata provides it.

Open bundled license inventory

PHP Runtime

Direct Composer packages used in Dollaroodle production code.

15 packages

PHP Development and Testing

Composer packages used for linting, static analysis, IDE support, and tests.

15 packages

JavaScript Runtime

Direct JavaScript packages declared in frontend runtime dependencies.

49 packages

JavaScript Development and Testing

Direct JavaScript packages used for TypeScript, linting, formatting, compilation, and browser tests.

7 packages

Platform-specific Build Tooling

Optional prebuilt binaries used to speed local and CI builds on supported platforms.

6 packages

With thanks

Open source is part of Dollaroodle's structure, not an afterthought.

We disclose it here because maintainers deserve to be named, licenses deserve to be respected, and software is better when its lineage is visible.

Product foundations
Runtime infrastructure
Test coverage and verification
Build and developer tooling