jquery/sizzle

A sizzlin' hot selector engine.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 10th, 2026
Created on August 24th, 2008
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 928
Total Stargazers: 6,301 (+0)
Total Subscribers: 284 (+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: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A 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

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Sizzle is a CSS selector engine that parses and matches DOM elements against CSS selectors.

The tool solves the problem of reliably querying the DOM using CSS selectors across different browser environments. It works by parsing CSS selector strings and matching them against DOM elements, handling the complexity of selector syntax and cross-browser inconsistencies. Sizzle provides a standalone implementation that can be used independently or integrated into larger frameworks to power their selector functionality.

Developers should consider Sizzle if they need a dedicated, battle-tested selector engine for DOM querying. It suits projects that require robust CSS selector support without depending on a full framework, or situations where selector performance and compatibility are critical concerns. The tool is particularly relevant for library authors who want to build selector functionality into their own frameworks.

The project maintains a stable codebase with infrequent but deliberate updates. Development activity is sparse, with long periods between commits, indicating the tool has reached a mature state where the core functionality is complete and requires minimal ongoing work. Issues and pull requests receive responses, though the pace of activity is measured rather than rapid.