fengyuanchen/cropperjs

JavaScript image cropper.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 4th, 2026
Created on September 25th, 2015
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 2,430
Total Stargazers: 13,888 (+1)
Total Subscribers: 167 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 532 days
Stale 30+ days: 24
Stale 90+ days: 20

Recent activity

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

Top labels

  • v2 (16)
  • enhancement (6)
  • bug (5)
  • question (5)
  • help wanted (3)
  • documentation (2)
  • v1 (2)
  • duplicate (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Cropper.js is a JavaScript image cropper library that provides interactive image cropping functionality for web applications. The tool solves the problem of enabling users to select and extract specific regions from images through a browser-based interface. It works by rendering an interactive overlay on images that allows users to define crop boundaries through mouse or touch interaction, then extract the cropped result.

Developers should choose this tool when building applications that require user-facing image editing capabilities, such as profile picture uploaders, photo editing interfaces, or content management systems. The project is suitable for any web application where end users need to frame or adjust images before upload or processing. The tool maintains a v2 branch for current development while keeping a v1 branch available for legacy support, allowing teams to choose their preferred version based on project requirements.

The project demonstrates consistent maintenance through adherence to semantic versioning and conventional commit guidelines. Development activity shows ongoing engagement with the codebase through structured commit practices and version management discipline.