nolimits4web/atropos

Stunning touch-friendly 3D parallax hover effects

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 19th, 2026
Created on May 11th, 2021
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 107
Total Stargazers: 3,603 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 83.1 days
Mean response time: 564.1 days
90th percentile: 1045.1 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,001 days
Stale 30+ days: 2
Stale 90+ days: 2

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

Atropos is a lightweight JavaScript library that creates stunning touch-friendly 3D parallax hover effects.

The library solves the problem of adding engaging visual depth to web interfaces through 3D parallax interactions. It works by applying rotational and depth transformations to elements based on mouse or touch position, creating an illusion of three-dimensional movement. The approach is designed to be performant and accessible across devices, with built-in support for touch interactions alongside traditional hover effects.

Developers should choose Atropos for projects that benefit from interactive visual polish, such as portfolio sites, product showcases, and gallery layouts. The tool is available in multiple formats to suit different workflows: as a vanilla JavaScript library, as a React component, and as a Web Component, making it adaptable to various tech stacks. The library is lightweight and free, positioning it as an accessible option for teams looking to add sophisticated effects without heavy dependencies.

The project maintains clear separation between development and production builds, with stable versions distributed through the package folder and development work isolated in a dedicated build directory. Development happens in the src folder with a structured contribution process documented in guidelines. The project provides multiple demo implementations across different frameworks in a playground folder, allowing developers to explore usage patterns before integration.