MengTo/threeui

Open-source ThreeUI Community catalog with live interactive components and complete Community source.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 12th, 2026
Created on August 21st, 2026
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 548
Total Stargazers: 5,671 (+0)
Total Subscribers: 22 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.1 hours
Mean response time: 11.3 hours
90th percentile: 29.4 hours
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 15 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

ThreeUI Community is a React component library that provides interactive 3D UI components built with Three.js and WebGL shaders.

The project addresses the need for production-ready, visually sophisticated UI components that leverage 3D rendering capabilities. It solves this by offering a curated catalog of components with live interactive previews, complete source code, and variant controls. The library uses the same application infrastructure as the commercial ThreeUI product, including responsive design, theming, search functionality, and a component browser with live renderers.

Developers should choose this tool if they want to incorporate 3D visual effects and WebGL-based interactions into React applications without building these components from scratch. The Community edition suits projects that need free, open-source components with full source access and no authentication requirements. The project explicitly distinguishes itself from the Pro version by removing Pro and Beta components while retaining all free variants and controls for Community components. Developers can install individual components via npm subpaths to minimize bundle size, though components that render full HTML documents require runtime assets to be copied into the application's public directory or configured via props.

Development activity shows consistent maintenance of the open-source catalog alongside the commercial product. The project accepts sponsorship to fund ongoing maintenance of the Community library. The team provides a public CLI tool for Pro members to authenticate and download entitled source bundles, using OAuth with PKCE for secure session management. The tool includes safeguards to prevent accidental overwrites of modified project files unless explicitly forced.