scalanlp/breeze

Breeze is/was a numerical processing library for Scala.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 20th, 2026
Created on July 8th, 2009
Open Issues & Pull Requests: 90 (+0)
GitHub issues: Enabled
Number of forks: 690
Total Stargazers: 3,453 (+0)
Total Subscribers: 196 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 299.6 days
90th percentile: 898.8 days
Tracked items: 3

Most active contributors

Sign in to see contributor activity.

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: 365 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

  • good first issue (1)

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

Breeze is a numerical processing library for Scala that aims to provide generic, clean, and powerful computation without sacrificing efficiency.

The library addresses the need for numerical and linear algebra operations in Scala by offering a unified interface for matrix operations, linear algebra, and related computations. It uses netlib as its underlying BLAS library for efficient native numerical operations, allowing developers to write numerical code in Scala while maintaining performance through optimized native implementations.

Breeze is suitable for Scala projects requiring numerical computation, linear algebra, or data processing tasks. The library is cross-built against multiple Scala versions, making it compatible with recent Scala codebases. However, potential adopters should be aware that the project is largely retired, with the original maintainer indicating they will only review bug fix pull requests and occasionally answer questions. This means the tool receives minimal active development and support, making it most appropriate for stable use cases rather than projects requiring ongoing feature development or rapid issue resolution.

The project has entered a maintenance-only phase with minimal active development activity. The original maintainer has indicated openness to handing off the project to someone willing to take over stewardship, but this has not occurred. Bug fix contributions are reviewed, though the pace and responsiveness of maintenance is limited.