2 weeks of work for the big redesign with lots of exciting new features!

[vanpelt]

Brief summary:

1. Big re-design making everything look much polished
2. Themes - we now use CSS variables to allow theming
3. Vision Indicators - models indicate if the support vision and we allow users to override our detection mechanism
4. Docker Image - we now provide a single docker image with each release
5. LiteLLM Support - OpenUI can support basically any LLM thanks to the LiteLLM proxy
6. Refine w/ Vision - We support asking for edits over a number of facets and provide a screenshot to LLM's that support vision
7. Desktop / mobile app support - we're now a proper PWA making for a nicer experience

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@playwright/test@1.44.1	None	0	25.4 kB	yurys
npm/i18next@23.11.5	None	0	635 kB	adrai
npm/monaco-editor@0.49.0	environment, network	0	93.8 MB	vscode-bot
npm/unsplash-js@7.0.19	environment, network	0	330 kB	unsplash
pypi/google-generativeai@0.7.0	environment, filesystem, network Transitive: eval, shell, unsafe	+21	179 MB	google-ai, google_opensource
pypi/litellm@1.40.22	environment, eval, filesystem, network, shell Transitive: unsafe	+282	1.99 GB	ishaan-jaff

🚮 Removed packages: npm/@uiw/codemirror-theme-vscode@4.22.2, npm/@uiw/react-codemirror@4.22.2, npm/cypress@13.9.0

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Potential typo squat	npm/openui@1.0.0	Did you mean: openuai (677 thousand times more downloads)	orphan: npm/openui@1.0.0	🚫

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/openui@1.0.0