anmolsaini16/mapcn

Beautiful map components. 100% Free, Zero config, one command setup.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 1st, 2026
Created on December 28th, 2025
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 701
Total Stargazers: 12,025 (-1)
Total Subscribers: 45 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.4 days
Mean response time: 15.6 days
90th percentile: 44.8 days
Tracked items: 38

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 19% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 178 days
Stale 30+ days: 10
Stale 90+ days: 9

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

mapcn is a library of pre-built map components for web applications.

The project addresses the need to integrate maps into web projects without extensive configuration or setup overhead. It provides ready-to-use map components that require minimal configuration, allowing developers to add mapping functionality with a single command. The components are built to be visually polished and immediately usable in production applications.

Developers should consider mapcn if they need to quickly add map features to a web project without managing complex dependencies or spending time on map styling and configuration. The tool suits projects where time-to-implementation matters and where developers want to avoid the learning curve of lower-level mapping libraries. The emphasis on zero configuration and one-command setup makes it particularly valuable for rapid prototyping or when map functionality is not the core focus of the application.

The project shows active development with regular commits and ongoing refinement of its component library. Work spans across multiple areas including component implementation, documentation updates, and codebase maintenance. The maintainer engages with the repository through consistent updates and appears responsive to the state of the codebase.