keras-team/autokeras

AutoML library for deep learning

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 15th, 2025
Created on November 19th, 2017
Open Issues & Pull Requests: 160 (+0)
Number of forks: 1,389
Total Stargazers: 9,326 (+0)
Total Subscribers: 289 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.8 days
Mean response time: 81.4 days
90th percentile: 272.9 days
Tracked items: 26

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 79
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,241 days
Stale 30+ days: 79
Stale 90+ days: 77

Recent activity

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

Top labels

  • wontfix (283)
  • bug report (182)
  • feature request (98)
  • pinned (93)
  • algorithm (37)
  • documentation (22)
  • good first issue (7)
  • performance (5)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

AutoKeras is an AutoML library for deep learning that automates the process of building and tuning neural networks. The tool addresses the challenge of making machine learning accessible to developers without deep expertise in neural architecture search and hyperparameter optimization. It builds on Keras and TensorFlow to automatically design, train, and evaluate deep learning models, handling tasks like architecture search and hyperparameter tuning without requiring manual intervention.

The tool suits developers and data scientists who want to apply deep learning to problems like image classification and text classification without extensive expertise in model design. It is particularly valuable for those working with structured data or image data who need a system that can explore the model space automatically. The README does not compare AutoKeras to alternative AutoML systems, so no comparative positioning can be stated.

The project maintains a substantial base of adopters, as evidenced by the fact that almost all open issues are raised by outside users rather than the core team. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker is dominated by bug reports, feature requests, and issues marked as welcoming contributions.