ApicurioArchive/apicurio-studio

Open Source API Design

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 45 minutes ago
Added to GitGenius on June 20th, 2026
Created on September 29th, 2016
Open Issues & Pull Requests: 368 (+0)
Number of forks: 511
Total Stargazers: 1,059 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.2 days
Mean response time: 184.0 days
90th percentile: 502.0 days
Tracked items: 28

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 859 days
Stale 30+ days: 27
Stale 90+ days: 27

Recent activity

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

Top labels

  • bug (5)
  • component/studio (5)
  • enhancement (4)
  • priority/normal (2)
  • priority/high (1)
  • priority/low (1)
  • proposal (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Apicurio Studio is an open source API design studio built with TypeScript and Angular that enables users to create and edit API designs using specifications like OpenAPI and AsyncAPI. The project is maintained at https://www.apicur.io/studio/ and serves as a comprehensive tool for API design and documentation workflows.

The repository is classified across multiple API-related domains including API design, API management, REST API standards, OpenAPI, API documentation, API editors, API collaboration, API lifecycle management, API modeling, and Swagger support. This broad classification reflects the tool's positioning as a full-featured platform for managing the complete API design process rather than a single-purpose utility.

The codebase is primarily written in TypeScript and uses standard NPM-based tooling for building and development. The project requires Node.js and NPM as core dependencies. Contributors are encouraged to follow established workflows including forking the repository, creating topic branches named after GitHub issue numbers, and submitting pull requests for review rather than patches. The project enforces code formatting standards through eslint to maintain consistency across contributions.

This interconnection indicates that Apicurio Studio exists within a larger landscape of API and development tools rather than in isolation.

The project actively welcomes community contributions and maintains a Zulip chat community for discussion and support. The contribution guidelines emphasize creating one commit per feature or fix using git squash techniques to maintain clean repository history and facilitate easier change reversion if needed. The README documentation provides clear instructions for getting started with the codebase, building the project, and the proper workflow for submitting contributions, making it accessible to new contributors interested in participating in API design tooling development.