mikeric/rivets

A lightweight data binding library.

View on GitHub ↗Jump to charts ↓

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

Summary Information

Updated 2 hours ago
Added to GitGenius on September 21st, 2026
Created on April 18th, 2012
Open Issues & Pull Requests: 140 (+0)
GitHub issues: Enabled
Number of forks: 300
Total Stargazers: 3,220 (+0)
Total Subscribers: 77 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.9 hours
Mean response time: 6.4 days
90th percentile: 12.0 days
Tracked items: 2

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,692 days
Stale 30+ days: 1
Stale 90+ days: 1

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

Sign in to see which issues are moving.
Sign in

Detailed Description

Rivets.js is a lightweight data binding library that automatically updates the UI when properties on bound objects change.

The library solves the problem of keeping views synchronized with data by subscribing directly to individual keypaths on objects and calling binder functions to surgically update specific DOM elements when mutations occur. It takes an agnostic approach, working with any object types or libraries through custom adapters, allowing developers to define their own adapters or use community-created ones as needed.

Rivets.js suits developers building data-driven views who want a minimal, focused tool without framework overhead. It works well in projects where you need reactive UI updates tied to object mutations but prefer not to adopt a larger framework. The library includes built-in binders for common tasks and supports custom binders, formatters, and adapters through its wiki, giving teams flexibility to extend functionality for their specific needs.

The project maintains a structured development process with clear contribution guidelines requiring bug reports to include isolated reproductions and pull requests to include test coverage for any changes. The build system uses gulp for compilation and minification, while the test suite runs through mocha with should.js for assertions and sinon for test doubles. The maintainers enforce discipline around the dist directory, committing built artifacts only during releases to prevent merge conflicts in contributor workflows.