moment/moment-timezone

Timezone support for moment.js

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 26 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 17th, 2026
Created on May 9th, 2012
Open Issues & Pull Requests: 47 (+0)
GitHub issues: Enabled
Number of forks: 839
Total Stargazers: 3,878 (+0)
Total Subscribers: 92 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.9 hours
Mean response time: 75.5 days
90th percentile: 30.2 days
Tracked items: 45

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 1
Closed in 7 days: 13
Avg open age: 1,719 days
Stale 30+ days: 7
Stale 90+ days: 5

Recent activity

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

Top labels

  • bug (16)
  • documentation (4)
  • New Feature (2)
  • TypeScript (2)
  • Up-For-Grabs (2)
  • add-time-bug (2)
  • planned (2)
  • Troubleshooting (1)

Detailed Description

Moment Timezone is a timezone support add-on for Moment.js that provides IANA time zone handling within the Moment.js library.

The tool solves the problem of working with time zones in JavaScript by extending Moment.js with timezone-aware date and time operations. It integrates IANA timezone data into Moment.js, allowing developers to parse, format, and manipulate dates across different time zones using Moment's familiar API.

Developers should be aware that both Moment Timezone and Moment.js are legacy projects in maintenance mode. The README explicitly recommends that in most cases, developers should choose a different library instead. This makes the tool most suitable for maintaining existing codebases that already depend on Moment.js rather than for new projects. Anyone starting fresh should evaluate alternative date and time libraries before adopting this add-on.

The project receives maintenance-level activity focused on sustaining existing functionality rather than expanding capabilities. Updates address bug fixes and compatibility concerns to keep the library functional with current JavaScript environments. The development approach prioritizes stability and backward compatibility for the established user base rather than introducing new features.