paulmillr/es6-shim

ECMAScript 6 compatibility shims for legacy JS engines

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 15 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 22nd, 2026
Created on December 25th, 2011
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 372
Total Stargazers: 3,099 (+0)
Total Subscribers: 94 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 239.3 days
90th percentile: 28.5 hours
Tracked items: 30

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,755 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

  • pull request wanted (9)
  • Spec compliance (6)
  • Tests (5)
  • needs followup (5)
  • repo management (4)
  • Promises (3)
  • Firefox / SpiderMonkey (2)
  • Collections: Map / Set / WeakMap / WeakSet (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

es6-shim is a JavaScript polyfill that provides ECMAScript 6 compatibility for legacy JavaScript engines.

The tool solves the problem of running modern JavaScript code on older environments that lack native ES6 support. It works by implementing shims—compatibility layers that replicate ES6 functionality in environments where it does not exist natively. This allows developers to use ES6 features without waiting for universal browser or runtime support.

The project suits teams maintaining codebases that must support legacy JavaScript engines while leveraging modern language features. It is particularly valuable for library authors and applications with broad compatibility requirements who want to use ES6 syntax and built-in objects without fragmenting their codebase or requiring transpilation for every target environment.

Development activity on the project is sparse, with infrequent commits and minimal recent engagement. Issues and pull requests receive slow or no response from maintainers. The codebase shows signs of age relative to the rapid evolution of JavaScript standards and browser capabilities.