About Senna
Senna's identity, upstream provenance, attribution, and compatibility policy.
Senna, by Bridgee
Senna is Bridgee’s React component library for building product interfaces. Its package identity is @bridgee-ai/senna; documentation is deployed at senna.bridgee.app.
Senna is named after the Ayrton Senna Bridge, which crosses the Paraná River. The name carries Bridgee’s idea of connection into the design system.
Fork and Attribution
Senna is a fork of Com Hora’s Clock, derived from audt.ai Judit, which is itself an independent fork of Kumo, originally developed by Cloudflare, Inc. and its contributors. Senna is maintained by Bridgee and is not affiliated with, sponsored by, or endorsed by Cloudflare, Inc.
The original copyright notice and MIT license are preserved in the repository. Historical changelog entries, commit authorship, and upstream links remain intact so that the origin of the work stays clear.
Cloudflare and the Cloudflare logo are trademarks and/or registered trademarks of Cloudflare, Inc. in the United States and other jurisdictions. Their names are used in these docs only for attribution, provenance, and compatibility references.
What the Names Mean
| Name | Meaning |
|---|---|
| Senna | The current product and design system |
| Bridgee | Publisher and maintainer |
@bridgee-ai/senna | Senna’s npm package |
| Clock | Immediate source fork |
| Judit | Source fork and retained provenance |
| Kumo | Upstream project and inherited compatibility namespace |
Some APIs, constants, semantic classes, CSS custom properties, and repository paths still contain Kumo or kumo. They are intentionally retained so existing applications can migrate incrementally and upstream changes can remain reviewable. New product copy and package imports use Senna; compatibility names change only through a deliberate migration with aliases and deprecations.
Curated Upstream Intake
Senna does not merge upstream wholesale. The retained intake script can open one downstream pull request for each new first-parent Kumo commit. Scheduled intake starts only when a maintainer enables it. Maintainers merge the changes that fit Senna, close the ones that do not, and apply Senna-specific adaptations in separate commits. This preserves authorship while keeping the fork intentional.